Try to use a timer instead of the Screen.Initialize event. It should work with the IPA.
Ups¡¡¡ NON and NON = YES.
You have right. With non Initilize Screen and whith a Timer Event to replace the Intilize Screen Event than I have not the 'environment' mistake.
But, the result when I execute the IPA is full different beetween Companion and IPA:
a) Whith Companion:
All is right.
b) With IPA build file:
Full wrong design screen as you can see on the images attached.
With iOS (Xcode/Swift) it's all quite tricky with the layout. In particular, "Stack views" and "Constraint"s are used here to arrange elements (relatively) to each other. This is anything but trivial. So you should avoid “Automatic” and instead set either percentage or absolute values.
Gracias @Anke ,
Before modifying all the screen designs while maintaining the integrity between Android and iOS (it is no easy), I would appreciate it if @ewpatton could inform us about when he can have the iOS IPA Compiler with iOS Companion at the same update level. I have all running welll with ios Companion 2.65.4. The problem is to have a old version for the IPA builder in version 2.64.4.
See also here:
The differences between iOS and Android are so significant that I would never think of arranging them together in a single AI2 project. And that's not just because I don't want to do without extensions on Android, but because of many other factors (layout, file system, storage architecture, permissions, standby mode (Android: Doze), app icon, File component (most methods only on Android), different media formats (and therefore completely different assets for iOS), ...
I have the full integrity between iOS and Android with the Companion runs but not with APK and IPA, I don't understand this topic. I think the compiler in Companion and the Builder Compilers are the same code
@Anke
The question is this:
I have one AIA running the same resultats whit Android Companion and the APK
And why not have the same resultats when I run the same AIA with the iOS Companion and the iIPA?
@ewpatton can we have the same resultat when I runs a same AIA with the iOS Companion ant their IPA file?
I think I have listed enough hints, aspects and problems.
1 Like
That means that always when I run a source code aia with iOS Companion I have a result but after when I will run the IPA file the result will be full different ...?. . Sure? May be whit my short English I don't clarify my real question.
Hello @ewpatton and Happy New Year,
The ios buid server show this initial message: el servidor de compilación de iOS:
Where is now the iOS Build Server Test for v 2.64.6?
Summary of my tests for iOS developments:
1-I have my app running fine on Android Companion and APK.
2-The same aia file from my app in iOS Companion also runs fine. I have had to put all the Layouts and Labels with height x width dimensions in fixed pixels and not use rolling or scrolling screens.
3-But the IPA file has the following errors when it is executed:
3.a) The initial problem of the "invoke environment object" has to be solved with the "botch" recommended by @Anke with a Timer that replaces the Screen.Initilize. But this is a job-stoper because we lost the integrited between ios and Android.
3.b) I get an initial "Invoke ShowListAsJason" irritating error. I don't understand this message because I am using all the lists as JSON with option checked in the project. In any case, the IPA runs without problems for this reason. See you the attached image:
3.c) Opening other screens does not work as reported by @anke. I have left only a single screen. See you the attached image:
3.d) The Screen1 option for scrolling screens does not work. I have left everything designed so as not to have scrolling screens.
4.). Is not possible close the app. I receive a message that is not possible in the development mode. See you the attached image:
@ewpatton what can you recommend to us? Thks
This isn't so much an error but a warning. When we set up test servers we usually set an expiration date when we won't officially support them any longer. Next time I push an update I will bump the date out further (originally I had hoped for the build server work to be done by Christmas but obviously that didn't happen). You can continue to use the test server in the meantime.
I'll add these to my list of bugs to investigate for built apps. I think there are two main bugs that have to be addressed before we can go live.
The first is around screen initialization and layout, which I think are tightly integrated in some way that needs to be tracked down. If everything is working in the companion it ought to work in the compiled app as well but the companion itself does some additional initialization work that maybe isn't happening in the right order in compiled apps.
The second is around screen switching. However, certain methods that work on Android may not translate well to iOS. For example, App Inventor implements screens as UIViewControllers pushed on to a UINavigationController's navigation stack. Therefore, closing and opening screens in the same event handler depending on the ordering of the blocks can cause issues.
Others may crop up but we won't know until we have more people using the system.
In the last few days I have been doing a number of tests regarding the layout of compiled apps (IPAs). Very few designer settings work. I had to do all the layout-related settings via blocks to get it to display properly.
I therefore assume that it also has to do with the initialization of the screen, which is not working properly (completely).
When it comes to screen switching, I noticed some other amazing things that I'll come back to later.
As problems to be solved, I would appreciate it if you also added point 4 that IPAs do not allow closing the App.
Only IPAs with ad-hoc certificate.
The iOS platform is increasing every year:
a) On the world near 29% of the market is iOS (the last years is clearly increasing).
b) In the USA near 61% of the market:
Yes, and it corresponds to my experiences over the last 7-8 years and my app sales in the Play Store and the App Store. I also experience it in my environment and my husband experiences it with his students. The proportion of iOS users is continuously and steadily increasing.
