-
Notifications
You must be signed in to change notification settings - Fork 101
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
Library fails to build on arm64 architecture #208
Comments
FWIW I've managed to semi-solve the problem based on this comment (#198 (comment)). It is, indeed, down to not using the .xcframework - by manually adding it into the project under However, I don't think is a great solution as CocoaPods should be able to handle this. I've tried various changes to get it to work, but I can't figure out why it's not integrating the correct framework properly. If I can sort this out I'm more than happy to submit a PR for it. @cjam do you have any suggestions? |
I came across this issue a couple months ago. Nice to see its getting some coverage - also using M1 |
Hey @wwdrew, Thanks for your work on this. Man, i remember it took me quite some time to get the cocoapod working correctly to pull in the framework from the package etc. I think the best way I found to debug the podspecs was to install the package and then go into the node_modules and update the podspec and then try to run I clearly should've documented something, because I'm trying to remember how I found to work on it the first time. |
Hi @cjam, no worries, happy to help out! You're not wrong about getting the framework working correctly being difficult, I've been playing with it off-and-on over the past few days and I still don't have it right yet :) One of the changes I've made was to remove the framework from the .xcproject and add the .xcframework instead, which updates the references inside the project, but the final step of actually getting the project to see it has still eluded me. I thought I had it working last night, but I was building on my Intel machine which worked already. I'll still keep tinkering and let you know how I'm getting on, but yeah if you have any suggestions I'm happy to hear them! :) |
I think I just got this working, but I'm not entirely sure which change I made caused it! Fingers crossed I'll crack it today. |
I've made a config plugin for Expo managed apps. Maybe someone will find it helpful as it took me some time to crack it, and couldn't find a solution anywhere else. Might need some tweaking to specific project, but basically it worked for me. index.js
withSpotifyRemote.js
ios/withAddedSpotifyRemotePod.js
ios/withAppDelegateMod.js
ios/withLinkedBinaryToProject.js
|
How can I use your plugin with my Expo app? |
@kvbalib you are a legend man, thank you so much for sharing! We should open a PR and submit the config plugin to the repo itself, so expo users will have an easier time! |
First get familiar with the development builds, then the config plugins. And then just add the path to the plugin's |
I’ve not had a chance to try this out yet but I’m heartened to hear it works. It’s funny, going back to this issue suddenly became really important this week, amazing timing! Completely agree this needs a PR. I’d still like to figure out how to get this original issue working though. I think the project is a couple of SDK versions behind too which would be nice to update. |
Hi, I've been testing this library out for a project and I'm having various difficulties with it. I've tried building the example application that comes with the package but neither one builds properly for me, so I've created an entirely new app which all it does is include the spotify-remote library, just to test whether it will build. The repo is here:
https://github.com/wwdrew/spotify-remote-testing
I've tried building this on both an Intel and M1 Mac.
At first I couldn't get Android to build, but patching the package using the latest commit in the repo has fixed it for both Intel and M1.
I can get my iOS test app to build in Intel, but when I try building it on M1 I end up with this error log.
I suspect this can be fixed by importing the
SpotifyiOS.xcframework
instead ofSpotifyiOS.framework
in the podspec. I've tried getting this to work on my local machine but couldn't get it working though, otherwise I'd have submitted a PR instead of an issue :)The text was updated successfully, but these errors were encountered: