@Anke
If I disable the Timer ONLY in the Screen2 and have enabled the Timer on Screen1 the app runs well and not have the fatal failure.
Wall is very curious-.....
Hi @Anke
I have tested several posibilities and I found a solution to not have the error:
1-I put all the Timers with the TimerAlwaysFire option disabled.
2-I Disabled in every Screen their Timer before go to other Screen. And I enable the Timer when every screen is accesed.
See you the attached AIA.
Whith this configuration I have not the fatal navigation error and I can the Timer active in every screen.
It all depends on the volume and importance of the errors detected and reported by all of us. @ewpatton is the responsible for the AI2 development team and he can respond better.
I've pushed a small update to the server that should improve access times for various web resources in built apps as well as fixing the issue where the project level iOS Settings were not being correctly propagated to the Info.plist file.
The iOS build server has been updated to 2.64.6 revision 5a with the following changes:
Make speech recognizer sensitive to user locale
Fix an error code in LocationSensor
Make clock methods sensitive to user locale
Make WebViewer fill parent when set to automatic width/height
Fix Delete method in Web component from sending non-capitalized HTTP verb that could cause issues with some servers
Provisioning profiles will now have their certificates and dates checked by the App Inventor server before a build starts in order to save time in the case they've expired
As I mentioned in the other thread, the design of this block was informed by the Android system in such a way that translating it into iOS is not really feasible. We have to think of an alternate way of accomplishing that.
I have updated the build server to version 2.64.6 rev 7. This update contains the following changes:
Report OtherScreenClosed when back swipe gesture is performed
Update the default iOS theme to DeviceDefault to match the same change on Android
Make use of new APIs introduced in iOS 13 to adjust the app-wide theme
Fix an issue with the spinner, datepicker, and timepicker not being readable when in dark theme
Add proper error codes for GoogleVoiceEnabled and ReceivingEnabled in the Texting component. These errors will only be reported in the companion app. Compiled apps will have them automatically silenced.
I tested this method now also on my iPhone 6s (iOS 15.8.2). There it doesn't work. (The same behavior as before, Screen1 pops up first...) So I have to do something like this
Regardless of whether ScreenOrientation = Portrait was set in the designer (or with blocks), the display rotates. To intercept (mitigate) the problem, there seems to be only this option:
Hmm. So I think the only way to "fix" this issue on iOS earlier than 16 will be to implement a custom back button rather than using the system-provided one.