Skip to content
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

[Feature Request] Support for Simulators on M1 Apple Silicon / arm64 architecture #810

Open
gustavoabel opened this issue Apr 19, 2024 · 5 comments
Assignees

Comments

@gustavoabel
Copy link

gustavoabel commented Apr 19, 2024

What's your feature request? Please describe.
Please support MLKit on Simulator with M1 Chip

Mobile environment
iOS with Xcode

@gustavoabel gustavoabel changed the title [Feature RequestSupport for M1 Apple Silicon / arm64 architecture [Feature Request] Support for M1 Apple Silicon / arm64 architecture Apr 19, 2024
@gustavoabel gustavoabel changed the title [Feature Request] Support for M1 Apple Silicon / arm64 architecture [Feature Request] Support for Simulators on M1 Apple Silicon / arm64 architecture Apr 19, 2024
@gustavoabel
Copy link
Author

@miworking3 Anything planned for this year?

@RogVok
Copy link

RogVok commented Apr 20, 2024

Looking at this comment: #691 (comment) this won't be addressed soon.

P.S. Since Julie would be in this thread, I'd like to highlight that many of us are still awaiting the ability to include MLKit models directly into the app's bundle, rather than requiring a separate download on each device (Digital Ink). This would greatly enhance user experience and convenience. (and will boost the satisfaction of working with Google MLKit)

@evandorn
Copy link

+1 I have to use Google MLKit for a project and I'd really like to compile my app natively for simulator on my ARM Mac.

@importRyan
Copy link

importRyan commented Jul 14, 2024

+1 When camera and GPU resources are unavailable, as in a Simulator, Apple throws errors or exceptions, but does compile those frameworks. It would be a massive win if MLKit and MLImage adopted the same philosophy as a shortcut to getting this arm64 arch exclusion removed.

For context, this is a blocker for us adopting a few CI vendors' technologies to automate our snapshot testing, so it's not just a save-some-time-compiling situation.

@importRyan
Copy link

Any visitors, also see: https://issuetracker.google.com/issues/178965151 and join in several years of commentary. :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants