Your english is fine!

Just to be clear, the "unofficial" package you are referring to has been created by Evan Bacon, the creator of Expo/Expo Router.

It will most likely become part of the official workflow at some point, and I never had issues with it.

If your only concern with it is that specific line in the README then I'd suggest trying it out first before jumping to conclusions, that's all. If you're already handling an app with "many complex targets" then you should have no problem understanding how to make Evan's plugin work in case you do stumble into any issues.

Cheers!

Your english is fine!

Just to be clear, the "unofficial" package you are referring to has been created by Evan Bacon, the creator of Expo/Expo Router.

It will most likely become part of the official workflow at some point, and I never had issues with it.

If your only concern with it is that specific line in the README then I'd suggest trying it out first before jumping to conclusions, that's all. If you're already handling an app with "many complex targets" then you should have no problem understanding how to make Evan's plugin work in case you do stumble into any issues.

Cheers!

For a new Expo user, this kind of user need would absolutely raise a lot of questions — they’d want to find even a single line in the Expo docs to make their uncertainty feel a bit more “certain.”

I’m really glad to hear from you that it works well in many projects. I already read through the expo-apple-targets source code two days ago and am prepared to customize it myself if it doesn’t meet my needs. Thanks for your “friendly” reply.

Lastly, I want to emphasize again that I hope the official Expo documentation can provide an official statement about this user need — instead of pretending it doesn’t exist. That would make things much friendlier for new Expo users.

You may be reading too much into how I write by I'm happy to help! ☺️

Evan has streamed a tutorial for it here and there is also this post on the official Expo blog.

Bro, I can use Google and the search function in Expo, and I’ve already spent a few days on this, so I’ve seen all the links you sent. Maybe I’m a bit grumpy because I woke up too early today, so my reply isn’t very “friendly,” but trust me I truly appreciate your response — at least it added a lot of certainty to my uncertainty, letting me know that these third-party solutions do work for you and some people in production projects.

However, I want to emphasize again: my goal from the start has been that the official Expo documentation should have an article addressing this user need — even if it just says there’s currently no official solution, and suggests how to solve it yourself or recommends some third-party libraries. That way, other new Expo users wouldn’t have to explore Expo under the same uncertainty I did.

Maybe I should summarize this long conversation so that other new Expo users concerned about this issue can have a “certain” answer when they came here:

As of now (2025-10-13), Expo does not have an official solution for this. However, most developers use expo-apple-targets to achieve it, so you can give that a try. If that doesn’t work, you can also use the bare workflow, keep your native targets, and using other Expo modules in your project.

I hope this words can provide some “certainty” for new Expo users confused about this issue.