-
Notifications
You must be signed in to change notification settings - Fork 6.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[V13] ERPNext mobile app status 404 #25213
Comments
Getting same error on my v13 production server. |
I get the same error (v13). |
Can confirm same error, has existed since January in the development branch as well. Have migrated to version-13 and same issue persists. Note that we have Certbot SSL Certificate installed for ERPNext site. |
In desk.js, there is an ajax function that called to This is returning a 404 error. What is the newserver uri? |
OK Solved it., almost. Change the complete code in desk.html to
|
Getting same error on my v13 production server. |
Update, since the 13.1.0 update the 404 error is gone, now getting 417 error |
Same 417 error |
Generated api call references 'desk' instead of 'app' calling get_desk_assets: /api/method/frappe.www.desk.get_desk_assets? Potentially related to changes deployed along with: frappe/frappe#11917 |
It just looks like a new app update needs to be pushed with the |
replicated on:
|
please refer to this comment for clarity on the issue frappe/mobile#47 (comment) |
Closing this issue since there's a repo dedicated to app development (see above). |
That repo is of another mobile application and not the one we use. |
Posting in a few places here on GitHub....wondering if there is any activity toward fixing the app for v13? I read that the app includes functionality to read bar codes / QR codes into fields...although I am unable to verify this functionality as the app fails with 417 error when I try to login. :-( |
Description of the issue
Both Android and iOS apps report status 404 on trying to login
Context information (for bug reports)
ERPNext/Frappe installation was updated from V13-beta to V13 release.
Output of
bench version
Steps to reproduce the issue
Observed result
"https://example.org failed with status 404"
Expected result
The home page
Stacktrace / full error message
From nginx server:
Additional information
Standard ERPNext installation.
The text was updated successfully, but these errors were encountered: