-
-
Notifications
You must be signed in to change notification settings - Fork 32
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
Failed to Compile; Includes inline assembly #19
Comments
Could be |
I think you are right - a quick google finds this Wonder whether I can remove altogether as not using SSL, very simple client MQTT connection (it is WatchOS afterall!)... |
I might be able to remove NIOSSL for watchOS builds, event for SSL builds. The iOS, watch OS builds don't use it, they use NIOTransportServices |
Thanks - that would be great. Meanwhile.... Set asm and removing all .s files. I forked this repo; removed package swift-nio-ssl from Package.swift. So far, runs, and has uploaded without error. Seems to fix issue currently. Obviously a bit messy; but hopefully a starting point. |
Do you want to try #20 |
Thanks - will test asap and update this |
Apology - clean and rebuild and okay now. Okay - all looks good. Seem fixed. |
#20 merged into main |
Describe the bug
Hi Adam
Thanks for this code - it is one of few mqtt libraries that I have found that is able to run independently on WatchOS. (which I need)
Testing and working well on both iOS and WatchOS 7, stimulators and devices.. Yah!
Unfortunately when i upload to Testflight: I receive this error:
ITMS-90562: Invalid Bundle - Bitcode failed to compile for your watchOS binary because it includes assembly source code or inline assembly. To resolve this issue, rewrite the corresponding code in a higher-level language such as Objective-C or Swift and redeliver your app.
At a guess it relates to the CCoreMqtt code? -- although can't find anything obvious.
Any suggestions or thoughts?
(Should mention - no other libraries/pods/dependencies, other than those needed/include with mqtt-nio)
Thanks.
The text was updated successfully, but these errors were encountered: