Mobile app occurs error

MK-R-J

Hi, support member!

Sorry if it's annoying to post so many.

I'm trying to test the AxonIvy iPhone mobile app in my company's environment.

However, while the login screen is visible in the browser, the mobile app displays the error shown in the image.

Error image:

Where should I start?

Environment:
AxonIvyEngine: 12.0.7
MobileApp version: 3.0.0

Thinh Nguyen

Hi MK-R-J,

Thanks for your question. I’ve tested it on my side and the connection works normally.
Could you please follow the steps in this documentation to set up the mobile app and try connecting again?

How to connect:
https://github.com/axonivy-market/mobileapp/blob/master/docs/How-to-connect.md

Let me know if it still doesn’t work.

MK-R-J

Thinh Nguyen

Thanks a lot.

I tried that from mobile app I log in axonivy engine. but I could not log in my engine, went something wrong.

I tried
1) Use the url https://my-company-server.com -> NG / error -> upper picture.
2) Use the url https://my-company-server.com/portal -> NG / error
3) add and use local user (like user:test / pass:test) & try 1) 2)-> NG /error
4) Use the url https://my-company-server.com/default/portal -> NG / error
5) Use the url https://my-company-server.com/default/portal/faces -> NG / error

Where should I look for logs, etc.?

etc:
I can log in to our company's axonivy Protal by a web browser in my phone.

Environments:
AxonIvyEngine: 12.0.7
MobileApp version: 3.0.0
Security Manager: Microsoft Entra ID (name:defalut)
Engine configuration:

Thinh Nguyen

Hi @MK-R-J ,
A convenient way to detect the correct application URL with the security context is by using the QR code feature inside the portal. Here is the documentation for it:
https://market.axonivy.com/market-cache/portal/portal-guide/12.0.11/doc/en/portal-user-guide/qr-code/index.html#howto-connect-to-the-axon-ivy-mobile-application-using-the-qr-code

Please try it and let me know if you encounter any errors.

MK-R-J

Hi. Thinh Nguyen

Thank you for your reply.

QR Code is nice function, but my phone app occurred the error of that picture if I used QR code.
sorry....

Thinh Nguyen

MK-R-J
Thank you for your message.

Sorry to hear that you encountered an error with the QR code on your phone app. The QR code feature is intended to help you easily determine the correct URL. If your device doesn’t support scanning it directly in the app, you can use an external QR code scanner (e.g., an online tool or another app) to read the code and get the correct login URL. Then, enter that URL manually in the mobile application.

MK-R-J

Thinh Nguyen

Thanks, your quick reply.

Upon checking, we found no problems with the QR code itself.

This is new information.
when we checked the nginx/Axonivy engine logs, the following error occurred in nginx.

nginx Logs (I have tried to log in the server from phone-app.)

2025/12/23 02:16:41 [error] 17#17: *12489 open() "/usr/share/nginx/html/api/engine/info" failed (2: No such file or directory), client: my-IP , server: localhost, request: "GET /api/engine/info HTTP/1.1", host: "my-engine.com"
my-IP - my-account [23/Dec/2025:02:16:41 +0000] "GET /api/engine/info HTTP/1.1" 404 146 "-" "Dart/3.3 (dart:io)" "-"

The nginx information referenced by our internal infrastructure team is found at the URL below.
https://github.com/axonivy/docker-samples/tree/master/ivy-reverse-proxy-nginx

What should we try?

Thinh Nguyen

Hi @MK-R-J,
Thanks for the update and for sharing the logs.

I reviewed the nginx error and it shows that the request to /api/engine/info is being served from the nginx static root (/usr/share/nginx/html) instead of being forwarded to the Axon Ivy Engine. That’s why the mobile app gets a 404 when it tries to load the engine info endpoint.

If you following the proxy.conf in example project, only the /demo-portal/ path is proxied to the engine.
Because the Mobile App completely communicate with the engine though API, it requires access to engine API endpoints like /api/engine/info, which the example proxy doesn’t forward.
I think to fix this, you need to update the reverse proxy to explicitly proxy API paths so they are forwarded to the engine, e.g.:
proxy.conf

location /api/ {
proxy_pass http://ivy:8080/api/;
proxy_set_header Host $host;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-Proto $scheme;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection "Upgrade";
}

You can check the rest endpoint path that need to forwarded in Engine Cockpit -> Services -> Rest services
Follow this documentation for more information:
https://developer.axonivy.com/doc/12.0/en/concepts/3rd-party-integration/restapi.html

Please try to edit the nginx config and let me know if you still encounter the error.

MK-R-J

Thinh Nguyen

Thank you for your reply.

We(Me and my company's infrastructure team members) successfully logged in AxonIvy Engine from phone app by local user.
but unfortunately by Entra-id user cannot log in.

We'll try to connect by Entra-Id security system, if possible, do you have any advice?
ex) nginx.conf related Entra-Id security system....

log
ipAddress - myEmailAddress [26/Dec/2025:00:35:38 +0000] "GET /api/engine/info HTTP/1.1" 401 86 "-" "Dart/3.3 (dart:io)" "-"
app error code : 401 HTTP 401 unautorized

MK-R-J

Thinh Nguyen

Sorry, I missed your comment.

You can check the rest endpoint path that need to forwarded in Engine Cockpit -> Services -> Rest services
Follow this documentation for more information:
https://developer.axonivy.com/doc/12.0/en/concepts/3rd-party-integration/restapi.html

Please try to edit the nginx config and let me know if you still encounter the error.

I'll read the documents.

Thinh Nguyen

Hi MK-R-J
The 401 Unauthorized indicates that the mobile app’s request reached the engine but was not authenticated, which aligns with the current authentication support in the mobile client. As of now, the Axon Ivy mobile application only supports Basic Authentication (username/password). It does not yet implement an OAuth/OpenID Connect login flow that would be required to authenticate via Microsoft Entra ID (or other third-party identity providers).
Because the mobile application is still under development, it currently lacks documentation and support for SSO/OIDC authentication flows, this feature is still planned for future releases.
Sorry for the inconvenience.

MK-R-J

Thinh Nguyen

oh....
Thanks a lot!
I understand that mobile app does not support Microsoft Entra ID (other 3rd party provider too) yet.

I hope it will be implemented soon!
Thank you!

MK-R-J

Thinh Nguyen

Thank you for the information you shared earlier. I have a few questions.

Could you please share the roadmap and development schedule?
What are your plans regarding support for third‑party security systems such as Entra ID?
Is there any official documentation for the smartphone application besides what is on GitHub?

Please let me know whatever you can disclose.

AlexSchaIvy

Thank you very much for your questions.

Regarding the roadmap and development schedule:
At the moment, we are evaluating the further development of the mobile application and defining the next steps for the roadmap. As soon as there is a concrete status or timeline, I will get back to you with more details.

Concerning support for third-party security systems such as Entra ID:
This is one of the planned topics within the ongoing roadmap evaluation mentioned above.

Regarding official documentation for the smartphone application:
There is currently no additional official documentation beyond what is available on GitHub. However, we are actively working on creating comprehensive official documentation.

Please feel free to reach out if you have any further questions.

Best regards,
Alex
Product Owner – Portal and Mobile App

MK-R-J

AlexSchaIvy

Thank you very much for your response.

I wish you all the best with the development!!

MK-R-J

Hi, @AlexSchaIvy

In our previous discussion, I believe the understanding was that as of January, things were still undecided, but that a roadmap and development feature schedule would be provided later.

If possible, could you share what the development plans are for the smartphone application as of June 2026?

In Japan, we would like to promote the use of Axon Ivy via mobile applications in our sales discussions where applicable. Therefore, it would be very helpful if you could provide a roadmap for mobile app development.

Also, would it be better to discuss this topic somewhere else instead of here?