Situation: A development device has been blinked up to a developer account with EI’s app, and is running a model. Later the same device is blinked up to the production account with our own app based on EI’s SDK, e.g. in connection with internal field-test.
Now the device is listed on the production account under a test software, and appear to running it, but actually it is running something else. If the model is changed and a build and run is performed, the device reboots, but does not load the revised model. It is also not possible to assign the device to another test software on the production account.
This takes quite a while to sort out every time it happens, especially when the person who blinked up the device ex. in an internat field test, is not the person trying to figure out what happens.
This has been reported as a bug, and the response was that it is a feature.
So here the feature request to please change this behaviour. Apart from being a major pita as described above, it appears as if EI is not in control of the system, and the same with the developers in the organisation trying to bring out products on the EI platform. From a system point of view I am sure it can seem perfectly reasonable, but for all intents and purposes it is experienced as undefined behaviour - a bug.