-
-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
iOS builds get rejected by the app store connect certification with issue ITMS-90426 #25
Comments
Hey @svenneve! |
That was the first thing I checked. It only happens when I add flex ui. I've tried all the hundreds of so called solutions, provisioning is set correct, tried adding a swift file so bridge headers get created, tried adding the folders and libs to the archive, tried always add swift libs to build option, etc, etc. The only thing that fixes the issue, is removing this asset, which i'll probably do as this has already cost me 2 days trying to figure out which asset is causing the issue and trying to get this asset to work. Last thing I'll try is an empty project with just this asset. |
Oh, ok, sorry about that. Maybe there's something wrong about the dylib build process 🤔
Please let me know the result of this, either if it works or not. |
I've tried with a super simple project, and the same issue occurs. Also, I'm not an iOS developer, so it could very well be I missed a way for it to be solved inside xcode. |
I guess it would. But if the plugin works in builds and the problem is only when uploading to the App Store, I don't know if there is much I could do, really =/ For the sake of trying, I'd say the XCode project would likely be more useful, but feel free to send both, maybe some Unity plugin could be messing up the XCode project up. |
Is this still an issue? |
Hey @YoavHortman. I have no idea, never submitted any apps to Apple using this package, @svenneve is the one who had the problem, not sure if they managed to fix it. It's possible the iOS dylib is built in a way that it shouldn't have been, building a static library may solve it. But I had lots of trouble building a static library for this package, since Unity also bundles Yoga, used by its new UI Toolkit. We can try again, of course. @svenneve does the error appear just by uploading the app to App Store Connect, without sending the app to review? |
I have not tested it on ios since then.
I suggest just adding it to your project and add a scene with flex on a
layout and build.
For all we know the problem is on my side.
Sven
…On Thu, Jan 9, 2025, 20:32 Gil Reis ***@***.***> wrote:
Hey @YoavHortman <https://github.com/YoavHortman>. I have no idea, never
submitted any apps to Apple using this package, @svenneve
<https://github.com/svenneve> is the one who had the problem, not sure if
they managed to fix it. It's possible the iOS dylib is built in a way that
it shouldn't have been, building a static library may solve it. But I had
lots of trouble building a static library for this package, since Unity
also bundles Yoga, used by its new UI Toolkit. We can try again, of course.
@svenneve <https://github.com/svenneve> does the error appear just by
uploading the app to App Store Connect, without sending the app to review?
—
Reply to this email directly, view it on GitHub
<#25 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAS3XH2G2FPNZNBFVUTOOFD2J3FETAVCNFSM6AAAAABU4UN42GVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKOBRGA4TQMZSGM>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
So, I found out this answer at Apple Developer Forum while searching for a completely different thing, maybe the problem is that we are using such a "naked" dylib instead of bundling it in a framework/xcframework. |
Using Unity 2022.3.23f1 and Flex UI 1.1.x
When I build my iOS project (XCode 15.4) with Flex UI in the project it won't get through Apple's certification.
Flex UI does something that requires SwiftUI but doesn't add the necessary folders/data, which prevents an app to be submitted to the app store.
ITMS-90426: Invalid Swift Support - The SwiftSupport folder is missing. Rebuild your app using the current public (GM) version of Xcode and resubmit it.
is this a known issue, or is there a workaround (besides using another flex-ui asset)
The text was updated successfully, but these errors were encountered: