-
-
Notifications
You must be signed in to change notification settings - Fork 625
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
Pods issue on macOS Monterey 12.0.1 #572
Comments
Can you try doing that and let me know how it goes? |
Yes. That worked. The value of 'minimum deployment target' was 10.11 [default] I changed it to 10.12.2 and that work with some warnings in the build process. The 10.11 warnings are: ld: warning: dylib (/Users/#####/StudioProjects/stocks/build/macos/Build/Products/Debug/just_audio/just_audio.framework/just_audio) was built for newer macOS version (10.12.2) than being linked (10.11) Thanks. |
I'm a bit concerned that this can happen in the official example when Apple releases a new version of macOS. I would have expected the example to continue to work due to backwards compatibility. Can you summarise which files in the plugin/example you changed? i.e. |
Hi @jonny7737 any update on this? |
Sorry, replied via email on 10/28. At pub.dev just_audio package under Tutorials is an article link
The article links to a github repo I copied main.dart and inserted that into a new flutter project. I see now that this is NOT the official example but is instead a third party tutorial. I apologize for my confusion on this item. |
I see, have you tried the official example and does it contain the bug you reported? |
Official example has the same result as reported in my second post: ld: warning: dylib (/Users/jonny/Downloads/just_audio-master/just_audio/example/build/macos/Build/Products/Debug/just_audio/just_audio.framework/just_audio) was built for newer macOS version (10.12.2) than being linked (10.11) And the build runs as expected. |
Below solution is working for me:
|
|
this worked for me |
Hmm, the official example already has
|
This is the warning I get even with '11.6.5' which is the Big Sur version my Mac is at right now. |
May I ask what version of Xcode you're using? |
Hi, it's Xcode version 13.2.1 (13C100) |
I may need to test that version of Xcode in order to reproduce this. |
Great! Thank you for looking into it. |
However, I can't say it's easy/quick, I'm short on storage space and the whole installation process usually requires me to do a painful game of musical chairs to make enough space to perform the installation. |
I can imagine. If it was a web issue I might have helped but I don't mess with Swift dev :) |
Alright, I did a search in the code to see where it was There are no warnings anymore. I don't know if there will be a nasty surprise waiting for me in some later process. |
@Ruzo would you consider making a pull request for that change? If you can verify that it works in your newer version of Xcode and I can verify that it works in my older version of Xcode, then I'll merge and publish it. (Although after that, I will definitely want to upgrade Xcode because Flutter 3 requires it. |
I made these changes in my own project's The only code that references |
Here my interest is in making sure the official example is fixed. Does the unmodified official example work for you as is? |
These are the warnings I get with the example:
I also found that you have |
That could be it... If you bump up that version, does it fix the warning? |
Fixing the |
The WidgetsBinding warning is separate from this issue, and I will commit a fix for that separately. Perhaps you are right about the cache. Can you try doing a |
I finally got to test it with different versions. Bringing the version down to So setting |
Interesting, although from memory the macOS implementation uses some APIs that require a higher version... |
So confirming with the Apple documentation, certain parts of the code do indeed require macOS 10.12, so I don't think lowering the it to 10.11 will be a correct solution. |
Maybe it has to do with checking for availability of macOS 10.11 in the |
That comes from the Apple API documentation's stated availability. However, I suppose since the plugin's podspec targets 10.12.2 or later, it may be a matter of simply editing |
Editing the |
I have finally managed to upgrade Xcode and I can confirm the issue does now happen for me. I'll take some time to investigate. |
After some Googling, it turns out that this is just a result of not completely upgrading the build tools when upgrading Xcode. Here is how I got it working for me:
After doing all of that, it now builds and runs successfully. There are still the same warnings, but after these steps, they are no longer fatal. |
Regarding the warning, it seems to be fixed by editing |
I've just committed fixes for the various warnings on the |
The warnings were never "fatal" in my case. With the
This warning only shows up on the first run after |
Yes I still have to fix the audio_session warning, although it's for a separate plugin so I'll need to address it over on that project. Regarding just_audio, did your fatal error go away with just the |
The |
Doing the |
OK, it sounds you already had most of the pieces of the puzzle already in place. Hopefully the above discussion will help people who stumble across the same error. |
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs, or use StackOverflow if you need help with just_audio. |
Which API doesn't behave as documented, and how does it misbehave?
Not an API issue. build of package example fails.
Minimal reproduction project
The example
To Reproduce (i.e. user steps, not code)
Steps to reproduce the behavior:
Error messages
Expected behavior
Expected example app to run.
Screenshots
No screens => no screenshots.
Desktop (please complete the following information):
Smartphone (please complete the following information):
Flutter SDK version
Additional context
I would very much like to try this audio player.
The text was updated successfully, but these errors were encountered: