Distribution build error

Solar2D iOS
#1

any ideas why I may be getting this error on ‘Transporter’ submitting an app (no changes to the app) since I uploaded it almost 2 years ago… No problem with any issues uploading it with Transporter 2 years ago … I just don’t get what can cause such a problem… when I changed no code in the app.

actually Transporter claims 12 errors on the upload attempt… but this was the top error listed. Maybe if I clear that error the others go away as well.

I did this build using solar-3710 and today 3711 Xcode 16.0 Mac M2 Pro OS15.0.1.

I did create a new provision profile for the app, as the previous one has expired.

Invalid bundle structure. “my.app/Frameworks/frameworkA.framework/Frameworks/frameworkB.a” binary file is not permitted. Your app cannot contain standalone executables or libraries, other than a valid CFBundleExecutable of supported bundles. For details, visit:

Thanks
Bob

#2

Ok … down to 9 errors … the 9 errors listed:
"STATE_ERROR.VALIDATION_ERROR.90087
"STATE_ERROR.VALIDATION_ERROR.90542
"STATE_ERROR.VALIDATION_ERROR.90171. (shows 5 times)
"STATE_ERROR.VALIDATION_ERROR.90125. (shows 2 times)

has any one experienced this error message ?

Thanks
Bob

#3

Since you haven’t built in two years, I’d suggest carefully reviewing your build.settings file, what plugins you’re using, etc. as well as everything on the (non-Solar2D) Apple side. You said you haven’t changed the code in two years which is probably the problem- things are always changing on the platform side.

#4

Thanks Colin,

I did actually try, striping out the only plugin(appodeal) from any module/scene where it would be referenced or used; as well as all references to it in the build settings. But, more upload tries all failed.

I figure the Appodeal Plugin when it is in the app and noted in the plugin section of build.settings - automatically updates to the latest plugin version when I build the app using the latest Solar2d 3711; so the plugin itself should fine; at least in the app.

So to your point, I may have to go thru everything in that older app build settings and double check everything on the apple connect side. Clearly something not ‘meshing’ between my build and the stuff at apple.

Thanks again for your input!
Bob