Status Update
Comments
sh...@google.com <sh...@google.com>
ka...@vivino.com <ka...@vivino.com> #2
do...@google.com <do...@google.com> #3
Sorry for the delay. Some of the necessary prerequisites are being actively worked on. Once they are in place, we can start addressing this issue.
cr...@sourcesense.com <cr...@sourcesense.com> #4
Thanks for the update! I'll be waiting for further news.
do...@google.com <do...@google.com> #5
Hi Cristina, to help us gauge the importance of supporting M1, could you share the size of your user base? And if you can also provide an App Store link to your app, that would be helpful too. In addition, I assume it's a simulator-only issue and you are able to test your app on M1 using a real test device (iPhone or iPad)?
cr...@sourcesense.com <cr...@sourcesense.com> #6
Hi there, the one I'm working on is an enterprise app, so it's not published on the App Store, my user base is about 600 users.
I'm able to test on a real device but I need to run with Rosetta to be able to use a simulator, that's indispensable to test on a wider range of devices that one may not have physically, that's a bit cumbersome. I hope this can be fixed before the end of Rosetta support.
cr...@sourcesense.com <cr...@sourcesense.com> #7
Hi there, since my team has started introducing SwiftUI in the app using this library this issue has became quite blocking for us since SwiftUI previews fail building regardless of Rosetta being enabled or not. I kindly ask you to raise its priority.
Thank you in advance.
ma...@gmail.com <ma...@gmail.com> #8
Even Rosetta is not the solution. Everything seems to work, but after a few minutes, strange errors start happening.
More info:
pl...@smartpatient.eu <pl...@smartpatient.eu> #9
If the problem is not solved soon enough, we will most likely abandon MLKit in favor of native solutions.
Our app is actually published, here's the link -
da...@dm.de <da...@dm.de> #10
ce...@jagcesar.se <ce...@jagcesar.se> #11
cr...@sourcesense.com <cr...@sourcesense.com> #12
Hello there, I just saw this issue was marked as a "Feature Request" and I'm concerned with this.
My definition of "Feature Request" is something that's not vital but would be nice to have, what we have here instead is something that's becoming more and more blocking by the day, with M1 Macs that will be the only Macs out there in a matter of time and SwiftUI that's taking over UIKit more and more and bringing such a dramatic increase in development speed that doesn't make sense to give up because this lib prevents SwiftUI live previews from working thus greatly reducing said development speed.
I kindly ask you to raise the priority of this issue.
Thank you!
ty...@tylerlabs.com <ty...@tylerlabs.com> #13
Ditto, would like this.
ja...@mbank.pl <ja...@mbank.pl> #14
cr...@sourcesense.com <cr...@sourcesense.com> #15
Hello, just passing by for a brief update: M2 is out and the last Intel Mac lineup is from 2020. Yet, still no Apple Silicon support.
ku...@gmail.com <ku...@gmail.com> #16
ro...@gmail.com <ro...@gmail.com> #17
ra...@gmail.com <ra...@gmail.com> #18
mi...@gmail.com <mi...@gmail.com> #19
Can anyone give some guidance on how to "ignore" GoogleMLKit/BarcodeScanning
when running on simulators for M1? I am new to iOS and especially to cocoapods. Right now the only solution I have is to open xcode in Rosetta whenever I need to test on a simulator.
aa...@konverto.eu <aa...@konverto.eu> #20
li...@gmail.com <li...@gmail.com> #21
[Deleted User] <[Deleted User]> #22
mi...@gmail.com <mi...@gmail.com> #23
I have replaced GoogleMLKit/BarcodeScanning
with Vision
's
ma...@gmail.com <ma...@gmail.com> #24
sh...@gmail.com <sh...@gmail.com> #25
va...@gmail.com <va...@gmail.com> #26
al...@mydario.com <al...@mydario.com> #27
ko...@gmail.com <ko...@gmail.com> #28
ag...@gmail.com <ag...@gmail.com> #29
ka...@gmail.com <ka...@gmail.com> #30
ty...@tylerlabs.com <ty...@tylerlabs.com> #31
I got tired of waiting, and only needed simple brace functionality, so I changed out the MLKit to a third-party BarcodeScanner library, and now I can happily run in M1 Sim. Oh well.
aa...@konverto.eu <aa...@konverto.eu> #32
ca...@truid.app <ca...@truid.app> #33
zr...@gmail.com <zr...@gmail.com> #34
ne...@macys.com <ne...@macys.com> #35
[Deleted User] <[Deleted User]> #36
va...@gmail.com <va...@gmail.com> #37
el...@openspace.ai <el...@openspace.ai> #38
fr...@gmail.com <fr...@gmail.com> #39
ja...@gmail.com <ja...@gmail.com> #40
ka...@gmail.com <ka...@gmail.com> #41
ja...@fareclock.com <ja...@fareclock.com> #42
+1
fr...@gmail.com <fr...@gmail.com> #43
You can follow this tutorial:
ha...@gmail.com <ha...@gmail.com> #45
ev...@eleostech.com <ev...@eleostech.com> #46
wo...@gmail.com <wo...@gmail.com> #47
id...@fidocredit.com <id...@fidocredit.com> #48
Thanks in advance
ka...@gmail.com <ka...@gmail.com> #49
ja...@fareclock.com <ja...@fareclock.com> #50
MLImage is still shipping iossimulator version with x86_64 only. Very frustrating this isn't resolved yet.
sa...@thevcgroup.com <sa...@thevcgroup.com> #51
+1
za...@gmail.com <za...@gmail.com> #52
ma...@jeanherfs.nl <ma...@jeanherfs.nl> #53
ca...@canpoyrazoglu.com <ca...@canpoyrazoglu.com> #54
ty...@gmail.com <ty...@gmail.com> #55
va...@gmail.com <va...@gmail.com> #56
ka...@gmail.com <ka...@gmail.com> #57
co...@mixbook.com <co...@mixbook.com> #58
va...@interlogic.com.ua <va...@interlogic.com.ua> #59
aa...@konverto.eu <aa...@konverto.eu> #60
May you answer us with an exact(!) ETA on when this will be done?
wi...@appwireinc.com <wi...@appwireinc.com> #61
id...@fidocredit.com <id...@fidocredit.com> #62
gu...@ridewithvia.com <gu...@ridewithvia.com> #63
sh...@gmail.com <sh...@gmail.com> #64
I am surprised this just needs a recompile, and has not been fixed!
ma...@gmail.com <ma...@gmail.com> #65
ka...@gmail.com <ka...@gmail.com> #66
mi...@totvs.com.br <mi...@totvs.com.br> #67
ka...@exitek.io <ka...@exitek.io> #68
ka...@gmail.com <ka...@gmail.com> #69
yo...@gmail.com <yo...@gmail.com> #70
kh...@gmail.com <kh...@gmail.com> #71
I have spent a week finding a solution/workaround for this issue (MLKit build on iOS Simulator). I have now finally been able to run MLKit (Translate) on the simulator. Please follow the steps below:
**Disclaimer:**
Up until now, I haven't faced any issues after adding the below configurations. If I find any issues, I will post them here.
1. The iOS simulator does not allow running arm64 architecture (arm64 in simulators is not like arm64 in real devices). So, in "Excluded Architectures": set "Any iOS Simulator SDK: i386 arm64" (use default) (include debug, profile, release).
2. MLKit does not allow running on 32-bit. We can configure it in Architectures, but it conflicts with iOS simulators as mentioned above. So, I configured it in Excluded Architectures: set "Any iOS SDK: armv7" (include debug, profile, release).
3. Add "Required device capabilities" in Info.plist with only the item "arm64".
Now my project can auto-run on iOS simulators (x86_64) and real devices (arm64).
You can confirm the final configurations from the attached screenshot.
Description
Hi, I'm experiencing an issue running an app that uses Google ML Kit Barcode Scanning sdk on iOS Simulator on a MacBook (MacBook Pro (13-inch, M1, 2020)) with Apple Silicon, here are the details:
ENVIRONMENT
STEPS
EXPECTED
The build ends successfully and my app runs on the chosen iOS Simulator
ACTUAL
Build fails with this error:
ADDITIONAL INFORMATION
This issue occurred to Firebase iOS SDK as well and it was fixed by creating a version of the pod specific for M1, here's the link:https://github.com/firebase/firebase-ios-sdk/issues/7175
By looking at the documentation now it seems the team was able to include the Apple Silicon support in the standard version so using an M1 specific version is no longer needed:https://github.com/firebase/firebase-ios-sdk/blob/master/AppleSilicon.md
Thank you, have a nice day!