I'm currently having the server add the audio background mode to every compiled app as a short term solution. Longer term we will need to implement a project level property to enable this so apps that don't need it won't get dinged by App Store review.
1 Like
Thanks for the explanation.
(Most of the time there are answers that you wouldn't have expected. 
)
Ok, but since I definitely need it for my app, I don't necessarily have to wait for this update. Correct?
But there's no problem waiting for the update either.
Correct. However, when the update goes out you will need to manually enable support for background audio in the new property. As usual I will make an announcement post when it happens but not until sometime in January as I haven't yet coded it.
1 Like
Hello @ewpatton
I had tested my app in the iOS Server 2.64.4.12 (3):
a) With Companion v. 2.65.4 (13) ALL is running well.
b) With the IPA build package Ad Hoc generated I have this initial error in my iPhone X with iOS v 16.7.4:
When we have the same level upgarde of the iOS COmpnanion with the build iOS IPA? (a date only planned will be good)
Thanks for your answer?
If I delete a lot of blocks and designs (until to have only one screen with few blocks) I receive the same initial mistake with the IPA file Ad Hoc.
I have only the Screen1 (no more, only ONE screen) and the Initilize block is not empty.
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?