iOS Undefined symbols architecture with latest update

[marcanw]

Compiling from Animate (AIR 50.2.3.1) on Windows for iOS get this error since I updated GooglePlayServices:

[marchbold]

Looks like we need to get Harman to update the stubs packaged with the AIR SDK again. I'll look into it.

In the meantime either use macOS to package your app or revert to the previous version.

[marchbold]

Which extensions are you using that is causing this error btw?

[marcanw]

Looks like we need to get Harman to update the stubs packaged with the AIR SDK again. I'll look into it.

In the meantime either use macOS to package your app or revert to the previous version.

I reverted back.
Can I update the other ane?

[marcanw]

Which extensions are you using that is causing this error btw?
I would say Inapp-Billing, according to the errors in the screen of the original post.

[marchbold]

I believe that is actually the core google firebase dependency in the error, so likely one of the extensions that depend on that.

The others you listed should be okay to update for ios, as long as you aren't using the FCM variant of push notifications.

[marcanw]

I believe that is actually the core google firebase dependency in the error, so likely one of the extensions that depend on that.

The others you listed should be okay to update for ios, as long as you aren't using the FCM variant of push notifications.

I use the FCM version. So I better avoid to update till there is a solution.
I ,just updated AndroidSupport. Is it fine?

[marchbold]

I would use the older versions of the androidx libs as well if you are trying to keep the same versions on android

[marcanw]

Hello @marchbold
Do you know when I will have a solution for this?

[marchbold]

Hi, I have been discussing potential solutions for this with the Harman team. The main issue is that the Apple opensource compiler for iOS apps that AIR uses hasn't been updated by Apple in a while and has fallen behind the features available in Xcode. So AIR is facing an issue with packaging iOS apps on Windows that use recent features in iOS or libraries that have been packaged with the latest build tools.

As there seems to be developers who don't want to or can't use macOS, I was wondering what you all would think of a hosted packaging solution for developers on Windows where a host provided by Harman would package your application for iOS and provide the ipa as an alternative. There would obviously be a cost involved (potentially part of the AIR license), but this would allow you to continue developing iOS applications on Windows.

Would love to hear your thoughts on this idea?

(Note this doesn't affect developers using macOS for iOS development)

[sjabberwocky]

I just bought a Mac Mini 2023 for iOS build packaging, but an alternative option would be nice.

[ajwfrost]

Well, there's some more information about the cause of all this, from the LLVM project:
llvm/llvm-project#56034

I'd just looked at the symbols exported by a framework with/without this flag, and there are zero differences other than those symbols being there! But of course, within the executable code, these symbols will be called in order to call each of the selectors...

So, it may feasibly be possible to build the "latest" Apple linker on Windows, and merge in the changes that LLVM have made, and then have this support these newly built libraries. But building the Apple linker on Windows was proving to be very complex already..

The alternative option -> providing a service whereby ADT would upload the object files to an online service, backed by a macOS computer that just does the linking -> might actually be simpler! but perhaps not quicker. And scalability may be an issue (and service availability, given how often our macs reboot themselves!)

[Ender22]

I'm a bit confused because I am packaging on mac with intelliJ but the latest com.google.firebase.core.ane ANE version is also giving me the same errors.

Does the latest require an update to XCode or something? I'm using a bit of an older xcode...

[sjabberwocky]

@Ender22 I also found that the latest update of Firebase does not compile and previous crush app on launch on iOS 12.5.5.

[marchbold]

@Ender22 Yes you need to update the compiler on macOS, easiest done by updating Xcode.

@sjabberwocky I'll follow up on the crash in the Firebase repo.

[Ender22]

Is it possible to update the compiler without updating xcode? I had a lot of trouble packaging on mac before, and right now it's in a 'if it isn't broke don't fix it' state.

I've downloaded xcode13 but can't install it without updating MacOS first. Could I like, just replace the path to the compiler to the new xcode13 one maybe?

If it doesn't work like that and would be a big hassle then I'll just bite the bullet and update the OS and xcode, but thought I'd ask first.