-
-
Notifications
You must be signed in to change notification settings - Fork 11
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
Ultrlytics HUB IOS app in IOS 18 stopped working. Is it only accessible in PRO plan? #864
Comments
👋 Hello @imranmu, thank you for raising an issue about the Ultralytics HUB 🚀! This is an automated response, and an Ultralytics engineer will assist you shortly. In the meantime, please check out our HUB Docs for detailed information:
For licensing and plan specifics, the documentation is your best resource. However, if you suspect a bug, please provide a minimum reproducible example (MRE) including any screenshots or steps to help us diagnose the issue accurately. You can find details on how to provide an MRE here. Thank you for your patience and collaboration in helping us improve! 🌟 |
@imranmu The iOS application is available to everyone for free - nothing changed. |
ok, thanks. But I don't see CoreML exported models and even default ones in IOS 18.1 on iPhone 15 pro and IOS 18.0 on Ipad pro (4th Generation). It seems issue with IOS 18.0. I was able to see it in IOS 17 |
Hello @imranmu, Thanks for reaching out! It sounds like you're experiencing an issue with viewing CoreML models on iOS 18. Let's try a few things to resolve this:
Feel free to share any additional details, and we'll do our best to assist you further! 😊 Thank you for your patience and support. |
Search before asking
Question
Previously we can see models on IOS in free plan. Is it only available now in the PRO version?
I cannot see it in the Ultralytics HUB app in the free plan. It would be good to state that in documentation so people have clear expectations. I cannot see exported models in HUB in IOS 18
Additional
No response
The text was updated successfully, but these errors were encountered: