Other issue,
11- This is very very corious issue. The block Timer for MakeInstant only runs well between the 00:00 to 12:59 in the iOS platform. If you put a time bettween 13:00 and 23:59 you will have a Fatal Error.
I attach you the aia file to test this issue.
I spent a lot of time to detect this mistake because all is running well in ANdroid but in iOS only runs well on the morning, in teh afternoon is not runnin well¡¡¡¡ @ewpatton : For this mistake I have not a possibility to do one workarround. To can follow testing will be necesary to have a new version with this mistake solved fpr your team. Can you delivery the fast correction?
Thanks
I have a mistake with the block of "Replace All Mappings" because it si not delivery to iOS in this current version.
Mr @ewpatton Can you tell me when will be delivered this option for your team?
Thanks
Other IMPORTANT issue:
12- Similar the point 7. I have a Notifier in Android running well. If I open this same aia in the iOS Platform then the "ShowChooseDialog" is NOT running well -tested with Companion- (it open and close with one second of delay, you can not read or select anything because is showed only 1 second). If you delete it in the iOS platform and write a new Notifier here, then it runs all well. It will be a serious problem to can maintain the same app in both platforms¡¡¡
For this type of conversion projects between platforms as different as Android and iOS, the re-engineering to be carried out is very important and for this reason I thank MIT for its great work since the incidents that are detected are of normal details.
More issues.
13-This is relative to write "defensive software" in the iOS platform. In Android these examples are running well when we have the follow blocks inside a Timer loop procedure every (1 sec). The same blocks in iOS have a random Irritant Errors with randoms "null lists".
a) In Android they are running always well, but in iOS both examples have random mistakes.
About the several problem in the issue Point 11. The mistake about the Timer block not running with times from 12:00 to 24:00 is also produced when the result of any timer is on time clock bettween 12:00 - 24:00. For example if you have a normal time before 12:00 and Add x minutes, if the result is a new time beetwen 12:00-24:00 you will have a fatal error for null instance.
Mr. @ewpatton for the problems with the Timer block (12:00 to 24:00) I don't have any posibility of workarounds to solve this issue. Please, can tell me when (more or less) can your team solve this AI2 mistake in the iOS Platform?
Regarding point 4 (Screen designs) the Notifier in iOS (now only in background color = white) has very poor visibility for the text. On Android it's better (the background in Android has only black as background color). See you the examples. Of course, we still have the compatibility issue betwwen both platforms if one only has a black background color and the other only white background color.
Hi @Ferran_SIMON, @dyjkim will review the thread and verify the issues. I'm not sure that we can address all of them (for example, iOS doesn't provide a way to change the background color of the alert view), but we can report back once we've tested everything.
I'm first tackling the layout issue for iOS, the layout mismatch between iOS and Android has been a complicated problem for a while and the team is working on with it. When we find a fix we will get back to you thanks.
Other issue,
14- This is not a important issue but I want to explain it to help somebody. In Android you can call the same Notifier inside the got response of it, for example in "After Text Imput" event. This is very interesting to verify texts formats inputs of the users app. For example:
Mr @ewpatton can you tell me about the problem with the Timer Component not running for iOS between the 13:00 until 24:00 when can be solved for your team?. This is a job stoper for my app because it use a lot of Timer components. Will be good, only a estimated planing date.
Thanks
I will see if we can get the timing issue resolved this week. Generally, if you can produce a simple test case that fails it is easier for us to debug rather than looking through the code for a full app.
I think you are ussing a 12:00 PM and AM Clock in you Ipohne (it is normal in USA). In EU is normal to use the 24:00 Clock. See you the Date-Clock parameter in my Iphone:
Can you verify the Clock parametrs in your Iphone if the problem is it? In Android I have also the same 24:00 Clock ans runs well, but in iOS Ihave and irritant null error on all the Timer blocks whne calculate Date-Time after the 13:00..
