Unsupported Architectures error in Transporter

After completing a new build of my app, when I attempt to upload to Apple using Transporter, I get this error:

Validation failed (409)
Unsupported Architectures. The executable for Play Trivia.app/Frameworks/AppsFlyerLib.framework contains supported architectures ‘[x86_64]’. (ID: 6f09234a-a5ff-45cc-88ad-90da1c332bd7)

Does anyone know what’s going on here?

Given that x86_64 only appears in the Apple simulator in Solar2D, I suggest you check your build settings and SDK sources, which is AppsFlyerLib, as well as their architectures.

@clang thank you for your response. I don’t use Native; only standard Solar2D, so I’m not sure what’s going on with AppsFlyerLib since it’s nowhere in my code. Any idea?

Will take a look can you post your build.settings for this plugin

I looks like you submitted a Xcode sim build instead, I also just pushed another build out for appsflyers, please try rebuilding and make sure you build for the store
Thanks
Scott

@Scott_Harrison ,
I am using latest Solar2D build,
I just tried build for AppStore and try to upload it with Transporter app.
still getting this error:

Validation failed (409)
Invalid bundle structure. The “MyApp.app/Frameworks/AppsFlyerLib.framework/AppsFlyerLib” binary file is not permitted. Your app cannot contain standalone executables or libraries, other than a valid CFBundleExecutable of supported bundles. For details, visit: https://developer.apple.com/documentation/bundleresources/placing_content_in_a_bundle (ID: 6d097732-943a-48aa-a9ca-1b5a58862157)

I am using this plugin:
["plugin.appsflyer"] = { publisherId = "com.coronalabs" }

@Scott_Harrison it appears that the recent builds CAN be created, but CANNOT be uploaded via Transporter because of the AppsFlyerLib plugin. We just removed it for now. But Scott, are you going to fix it?

FYI, when I removed the appsFlyer plugin, the problem disappeared. Are you going to fix the problem with including it?

Also, it was NOT an Xcode sim build.

@troylyndon @BK_PANARA There was an update to the Appsflyer plugin two weeks ago. Have you tried building with the version of the plugin that predates that update to see if that one still works?

["plugin.appsflyer"] =
{
publisherId = "com.coronalabs",
version = "v16",
},

Obviously, it’s not a permanent solution, but if you need to get an update out and don’t want to lose Appsflyer’s functionality, it will at least keep you going while the library problem gets sorted out.

@colinmorgan , that works :slight_smile:

1 Like

Will take a look at this again tomorrow

Update went live and the update fixes app transporter issue