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
Class AMSupportURLConnectionDelegate is implemented in both ?? (0x1eb0e27a0) and ?? (0x1296d02b8). One of the two will be used. Which one is undefined. #72492
Comments
Hi @yvngaayush Related #72142 |
The flutter run --verbose log is attached. This is a project I had worked on my old computer and it runs perfectly fine. Just not running on my M1 mac, with that error shown earlier. |
Same issue here! Here are the logs similar to the post and hope that would be useful.
When I
Skip many warnings on the lib target version.... then at the end, these errors display red
|
I think it is a bug with the M1 mac, not sure what to do... please let me know if you figure something out. I've tried a bunch of stuff. |
I encountered the same error on a M1 Mac Mini and with the stable channel. My issue is that I can't use the master branch on my project, so I'm stuck with this. |
@Nolat Is it the same issue you faced? @yvngaayush @amoslai5128 Thank you |
@TahaTesser Yes I've got that error when trying to run the app on an iOS Simulator.
|
I'm not seeing this on either stable or master with just a fresh flutter doctor -v
|
flutter doctor -v:
Still has some errors
|
Same output as @amoslai5128. And @markusaksli-nc, yes no issue with a new project, but after I try to transfer some files even from an existing project that compiled fine in my old computer onto the new project, it still gives this error after a certain point. Not sure... |
Yes, only error builds with the M1 currently. Also, the same error output after I updated to Big Sur 11.1 and XCode 12.3. |
@amoslai5128 have you found a solution? Nothing is working |
+1 to this issue, just started happening (also M1) |
Not yet, not working for me too. |
I'm back up and running. unfortunately don't have a perfect list of steps of what I did (nor what worked vs had no effect). I opened the project in xcode and tried running there, eventually having to solve a number of errors. This might have been the crucial step, if/when you hit this error: Good luck! |
A way I found that I can continue to develop is you can run the flutter app
on Chrome just fine. Not ideal but works until this issue is resolved.
Could you outline what type of things you did? If you remember.
On Sat, Dec 19, 2020 at 3:11 PM Joe Polin ***@***.***> wrote:
I'm back up and running. unfortunately don't have a perfect list of steps
of what I did (nor what worked vs had no effect).
I opened the project in xcode and tried running there, eventually having
to solve a number of errors.
This might have been the crucial step, if/when you hit this error:
facebook/react-native#29984 (comment)
<facebook/react-native#29984 (comment)>
Good luck!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#72492 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AH4K5NPOCMDP6D7ZQ7OS4Z3SVUCFPANCNFSM4U7APFKQ>
.
--
*Aayush Shah*
(407) 985-8389
|
Worth mentioning that I saw this just once when running |
Same issue. Used to work before the OS upgrade to 11.1 (from 11.0). Now doesn't work on any branches. |
OK I resolved the build. This error is misleading because it is not actually the reason why the build is failing. There were other non-related errors such as missing firebase info plist files that are causing my build to fail due to some configuration issues. Once I fixed those, this issue automatically resolved. |
If you notice your build error logs, the real reason for the failure is here:
The solution is here: #70895 (comment) |
thank you |
I did the above solution, and the build is still failing.
Anyone know how to fix this yet? |
I'm facing the same issue
|
I resolved the issue, not sure which one did the work. I remember also running this |
Not working @fauzipadlaw |
Just in case anyone is still facing this issue.. just ignore this error message, it's not the reason why your build is failing.. Look for other error messages in the log and fix those. That will resolve your build problems. |
|
This is the issue. It couldn't find /outside Did you name one of your folders with a space? It seems the build sequence cannot handle folder with spaces in them. |
Oh |
is a warning from Xcode command line tools that have been emitted for years. It's confusing, but it's never the reason your build is failing. We're tracking showing better error messages from Xcode with #22536. I'm going to close this. You're all hitting totally different errors, and you need to file separate issues with As @joniaiuser has pointed out, @yvngaayush and @amoslai5128 hit #70895. |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
@abdullah432
Xcode clearly states when something is a warning or an error and errors are usually at the end of the build logs because the build stops when an error is encountered. |
|
I resolved the issue, It was my first time trying to run an application on Macbook. It was firestore configuration issue. I follow firestore configuration guide but later turnout, the developers are no longer need to follow that guide. I removed it and now everything is working. Thanks for your time. |
Can you found the solution? |
@prasath95 To find your issue. Open your project on xcode and run through there. Your build error log will show you the real problem. |
This comment has been minimized.
This comment has been minimized.
|
Output when I run flutter run on my new M1 Mac:
I have tried deleting cache and pod files. Been trying to fix this for a couple of days.... :(
The text was updated successfully, but these errors were encountered: