Multi-platform conflicts? Preferences

[cusingerBUSCw5N]

I have just set up my app to be tested in an IOS environment.... and now it is broken on the Android side.

I developed the app on a PC. I bought a MacBook to modify it for IOS. I installed LiveCode for IOS on the MacBook. I ftp'd my app to the MacBook. I set up the MacBook for IOS development, which involved puttiing a setting in Livecode preferences pointing to Xcode and then setting some fields in the standalone applications settings so that it could use the simulator. The app appeared to work fine in the simulator.

Then I ftp'd it back to my PC because I didn't want to have to put all the settings in each time I modify it during the testing...

Now, the native controls won't work on an Android and it won't go from card to card on an Android (it will on the laptop). It will let me click buttons and it will perform steps that are on that card - but it won't go anywhere else and it won't create any native control fields in a mobile environment.

Is there a simple fix here, or do I need two separate development environments so that one doesn't corrupt the other?

[FourthWorld]

Because it works for you on iOS and the issue you're having is on Android, I've deleted your duplicate post in the iOS section of this forum.

In the future please post a given message only once. Thanks.

[jacque]

You shouldn't need to write two versions. Failures can happen if there are iOS-specific commands that either do nothing on Android or cause a script error that aborts the script. Simple navigation commands shouldn't do that though. Can you post an example of a handler that is failing?

[cusingerBUSCw5N]

My blackout was caused because I referred to closing a field that didn't exist in on closecard. I am using native controls that have to be destroyed at the close of a card and also require an invisible field so that the keyboard closes. I forgot to put the invisible field on the home page - so it never left that page. Likewise, my code mis-spelled the name of a native control, so it wouldn't create it.

Bottom line - as usual, my error.