Activities of "improwise"

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 doctor command 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.

Seriously, this service bot needs replacing :)

Having looked at this again more in detail, we still feel that the React Native / Expo template provided is still no where near production ready. Lots of configuration error, dependency on modules that have been deprecated for a long time etc. Honestly, I don't see how this could be missed in this supposed new and updated React Native/Expo template when just running Expo doctor would show many of the problems immediately.

Since project configurations can impact npx expo-doctor results, providing a minimal reproducible example would allow us to assist more effectively.

Unless something has changed since I created this thread, just create a new ABP project and try to run the Expo Web is enough.

With the now improved mobile navbar (ordinary hamburger menu to the right rather than that hideous big icon in the middle), I think most customers would be happy if we just had some basic control over what is displayed there and in which order rather than feeling the need to change the entire component in itself.

While you are at it, would also be good if there was some simple settings to hide languages, appearance etc. and also that they were a bit more context aware, like why display the language bar if only one language is available etc. Ideally, also being able to disable some of the themes, seems like even if you set the default to one theme in code, it will still override with system setting, at least for Angular which isn't ideal.

You're absolutely right to raise this concern. The current setup limits flexibility at some point, and we recognize the need for better control over these options. We will be including the enhancements in the upcoming releases. We appreciate your feedback—it's valuable in shaping a more practical and adaptable LeptonX experience. Thanks for your cooperation!

I assume this also means that I am correct in that in order to modify this, even if it is just to change only what "icons" are displayed in the mobile navbar, you would really have to make a new version of the entire mobile navbar component?

While possible, I had a look at it and it seemed like it would be a quite daunting task which would also need to be repeated with every new update which isn't doable in the long run. This at least for the Angular UI, but I imagine it would be something similar with all UIs.

If this is something you decide to put into the future task list (which I think you should), please refund this ticket.

Thanks.

What is the reasoning that a mobile user would not need to login but a desktop (big screen) user would? Especially as it seems that empty slot in the mobile navbar is not used for something else until you actually find a way to login.

As I understand it, in this case, the only way to affect this would be to do as you say with component replacement. Considering this is a quite complex component/module, this would in reality mean that you would need to download the source code for LeptonX and make you own version of the entire mobile-navbar component to get support for dynamic menus etc. And all this just because you wanted to change the menu items displayed in the mobile navbar. And this would have to be repeated for every new ABP project.

What would actually be needed is a way to control what menu options are displayed on the mobile navbar (besides the hamburger menu), just like you can for the main menu system. I find that the LeptonX theme looses a lot of practicality because of this.

Or am I wrong?

Hi,

dynamic-env.json is not necessary getEnvConfig API request is related to RemoteEnvironment. You could remove the configuration if you didn't use it. https://abp.io/docs/latest/framework/ui/angular/environment#remoteenvironment

It can work with any webserver , not just nginx.

But isn't the dynamic-env.json file there only to be overridden by the one in docker-compose folder (or rather on a mounted docker volume)? And the same probably goes for the nginx.conf file. If so, perhaps it should be highlighted more in the docs, as I think trying to setup something similar in a production environment, especially a managed one, would require different solutions (since you would probably not control the host to be able to modify the local docker-env.jsoin).