Since obviously no one at ABP is working on this and probably never will, perhaps we should go ahead and close it?
If only the service bot could be trained to solve tickets instead of just closing them.
[sumeyye.kurtulus] said: Hello again,
Yes, we are still supporting the React Native template. We will soon be focusing more closely on it to align with the latest features and address any potential issues or degradations. In the meantime, the templates remain safe to use.
Not to be that guy but the same was said 5 months ago as well.
5 months later now and still no one at ABP seem to be working with this (at least based on the non input in this thread).
Isn't it just easier for everyone to say that there is no support for React Native / Expo in ABP anymore and that there are no plans to reintroduce it? Or am I missing something here?
@EngincanV
4 months later and the only one working on this seems to be the service bot.
Seems not even ABP staff can control the service bot :)
Reopened again
Please stop closing unresolved issues.
Thank you for reaching out again. The current React Native template remains supported, and the issues you’ve pointed out are actively being managed. There should be no problem with using and publishing apps at this time. Running the
expo doctorcommand can help ensure compatibility with the latest updates.That said, the template continues to be a priority, and we are consistently testing and refining it. We appreciate your patience and feedback.
After some struggle we were at least able to get this running (except for the Web version as reported above). There are a few things missing in the docs on https://abp.io/docs/latest/framework/ui/react-native on how to do it. This is from memory so could be a few more steps I am missing here
You need to run Expo Doctor ("npx expo-doctor", not "expo doctor") and fix the most obvious problems
As mentioned in the docs, you need to user your local IP instead of localhost. Besides what is mentioned in the docs, you also need to update the config for the _Mobile Application in DBMigrator (replace localhost with same IP)
You need to make sure that the API can actually be reached using HTTP and not only HTTPS as that is what is used by the Expo app. Just getting your web browser to accept the SSL cert is not enough.
Note that the Expo app is setup to be run on port 19000 by default and the config is setup to match this. This is mentioned in the docs but might still not be obvious to anyone used to doing "npx expo start" etc. You could probably change ports in config as well an run it normally also or just specify port in npx expo command.
Some things we could not get to work
Web. This needs to be fixed as it makes it much more efficient to develop, at least assuming your app is something that works in the web like CRUD.
We were not able to get the development build running, only Expo Go. Did not look too much into why but this needs to be fixed (assuming it is an ABP problem) as Expo Go is far from ideal for serious development. Edit: We were able to get this working with some tinkering.
Any news on this? Sorry to be that guy but I honestly think ABP should consider for the time being remove the claimed support för React Native / Expo as I can't imagine anyone using the current template with the problem it has. Also the fact that it hasn't really been a working template for months now.
At least provide us with an update from management team if React Native / Expo is even a priority anymore. This "coming soon" is starting to feel more like never. Thanks.
Hi,
It was mainly while we continued to evaluate/use the Docker support ourselves but we have paused that for the moment anyway. Hopefully our findings can help improve the needed files for everyone.
