i dont run simulator, expo 51.4.0 . I dont working with send link, please help me. i cant test local
Guys chill. It’s a stupid stunt apple is doing here, but you can just use the camera on your iPhone to scan the code. First thing I did after seeing the button disappearing.
Cya
thaNKS A LOT NOW WORK FINE
It’s really a strange decision. If the way QR scanning was used in expo isn’t allowed, then no QR scanning should be allowed in IOS apps at all!
Meanwhile, to expo team - I remember I could just type the ip address i.e. exp:// ... and I see no way to do it now, am I missing something? Thanks.
This is absurd, why can’t we just type the URL into the Expo client? Why all the nonsense with QR codes and text messages?
hey people, I agree this is very unfortunate! we are just doing what we had to do in order to comply with app store guidelines, and there isn’t a lot of opportunity to have a back and forth conversation with apple on this because we are still very small and make them basically no money. we’re working hard to get some better connections at apple so we can have productive conversations with them and hopefully one day restore functionality that we have had to remove 
we’re going to be rolling out an update to the ios client soon that will sync projects open in development to your expo client app. you can try this on android already, or in the ios simulator. just sign in to the app to the same account that you’re using in exp. check out this screenshot – the project i’m pointing to in the client showed up there automatically.
4 Likes
First off, kudos to the team on handling the issue. As others mentioned, more warnings (perhaps in-app for the Expo client) would have been great, though.
However, I’m not sure I understand how guideline 3.1.4 means that “Expo Client can open those projects only if they belong to you, i.e. when you’re logged in to the same Expo account that authored the project” if doing so by entering a URL instead of scanning a QR code?
Loosing the QR code scanning is obviously annoying, but manageable. Loosing the ability to distribute test builds easily to testers/clients through a simple URL, bypassing the horrendous TestFlight system, is more than just an annoyance, though.
I have same problem. My customer can’t open app from sharing system It’s not working anymore. Now we quick resolve a problem then We shared email between customer and developer (Multiple Login at same time it’s work).
same problem appeared on latest version also i fixed it by scanning with device camera
However, I’m not sure I understand how guideline 3.1.4 means that “Expo Client can open those projects only if they belong to you, i.e. when you’re logged in to the same Expo account that authored the project” if doing so by entering a URL instead of scanning a QR code?
there was another cited guideline which i don’t have handy at the moment but it was about using the app for test build distribution, and we had to interpret what this meant for us and re-submit a build. we may have overcompensated and removed more than we needed to (perhaps we could have left the + button) but we did this to reduce risk of getting the update rejected as we really wanted to push out sdk 26 – many users needed this update for various new features and fixes. as we build better relationships at apple we’ll try to find out exactly which compromises we need to make and not make in order be compliant with the app store.
Now that the new release has been accepted by apple can you release the + option again. If it gets rejected at least there is a stable sdk 26 still available.
If not I have two suggestions that I believe would help developers.
- Is it possible to have a read only account. I have created a second account that I publish my app to and have given the details to anyone that has contacted me about this but it’s feasible that someone could delete the app that I installed there.
- Is it possible to have a custom warning when people try to reinstall the app so that I can either give people my email to get in touch with me or give them details to the second account i mentioned so they can install the app through that.
Cheers,
Keep up the good work!
We may be able to add back the “+” button but we would likely keep the restriction that you can load only projects you are working on. Having the app get accepted is also not a guarantee that the feature is considered compliant with the review guidelines. We want a good relationship with Apple and submit updates in good faith.
Regarding your suggestions, if you would like to share your project outside of your collaborators (e.g. testers), Apple has suggested you use TestFlight. I may be misunderstanding your second suggestion, but it sounds like people who download the Expo Client would need to indicate they are associated with you in some way in order to see the message. I don’t foresee us building a feature like that; if possible, you could contact the people who use your project and let them know about a TestFlight build, for example.
As a reminder, we ask that all content published to Expo generally follow Apple’s guidelines as well:
In addition to providing an environment for developers to learn, collaborate, and share with each other, Expo also provides a service for hosting your projects. We apply a slightly different set of standards to projects hosted on our service. At a minimum, your projects should respect:
Apple’s “Safety” and “Intellectual Property” criteria from the App Store Review Guidelines
Google’s “Restricted Content” and “Intellectual Property, Deception, and Spam” criteria from the Play Store Developer Content Policy
I hope that adding back the option for users other than yourself to access your expo.io published projects is a priority. To me, this is one of the main assets of Expo, and an awesome tool to have during the development process. Sure, Testflight exists, but it’s a hot mess of a burden in comparison, and I’d rather not go back now that I’ve gotten used to the bliss of Expo.
4 Likes
This topic was automatically closed 15 days after the last reply. New replies are no longer allowed.