Skip to content
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 417 #25537

Closed
wazhanudin opened this issue Apr 30, 2021 · 12 comments
Closed

[V13] ERPNext mobile app status 417 #25537

wazhanudin opened this issue Apr 30, 2021 · 12 comments
Labels
bug to-validate Old issues pending validation

Comments

@wazhanudin
Copy link

Description of the issue

Both Android and iOS apps report status 417 upon login

Context information (for bug reports)

Had no issue with
ERPNext: V12.20.0
Frappe: V12.17.0

Output of bench version

erpnext 13.1.1
frappe 13.1.2

Steps to reproduce the issue

  1. Open ERPNext app
  2. Enter ERPNext url
  3. Attempt to login

Observed result


erpnextv13-error417

Expected result

ERPNext home page

Stacktrace / full error message


Additional information

Fresh install (Standard) from auto install script.

OS version / distribution, ERPNext install method, etc.
Ubuntu 20.04.2 LTS

@wazhanudin wazhanudin added the bug label Apr 30, 2021
@Olawale1
Copy link

Olawale1 commented May 1, 2021

Encountered the same issue...

@MPI-Olivier
Copy link

I have the same error.

any resolution on this issue?

@johnsonwhl
Copy link

johnsonwhl commented May 4, 2021

i've got the same error with bitnami ERPNext 13, no issues on bitnami EPRNext 12

@dxgerp
Copy link

dxgerp commented May 5, 2021

Duplicate of #25213
Generated api call references 'desk' instead of 'app' calling get_desk_assets: /api/method/frappe.www.desk.get_desk_assets?
vs
/api/method/frappe.www.app.get_desk_assets?

Potentially related to changes deployed along with: frappe/frappe#11917
feat(routing): New routing style, not using hashes, also /desk -> /app

@wazhanudin
Copy link
Author

wazhanudin commented May 8, 2021

erpnext 13.x.x-develop
frappe 13.x.x-develop

Accidently updated to this version..
Error 417 still persist with latest version of erpnext & frappe

@krnkris
Copy link
Contributor

krnkris commented May 8, 2021

Same issue.
Only reachable in a browser.

@buff0k
Copy link
Contributor

buff0k commented May 19, 2021

Reproduced on:
erpnext v13.3.0
frappe v13.3.0

This appears to be an evolution of the earlier issue (404 error)
#25213 (comment)

Appears that the api call in the app is wrong.

@sumitbhanushali
Copy link

please refer to this comment for clarity on the issue frappe/mobile#47 (comment)

@buff0k
Copy link
Contributor

buff0k commented May 31, 2021

Can also confirm issue persists in 13.4.0

@egauravjain
Copy link

Same issue for the following version:
ERPNext: v13.5.1 (version-13)
Frappe Framework: v13.5.1 (version-13)
Any resolution/workaround in sight?

@Harshavardhansaigit
Copy link

I have installed latest erpnext(13) in my mobile . Im getting "failed with status 417" while i'm login into my account in mobile app but i can able to login in my mobile web.

@infinity-sys
Copy link

I confirm same error

@ankush ankush added the to-validate Old issues pending validation label Dec 10, 2021
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jan 28, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug to-validate Old issues pending validation
Projects
None yet
Development

No branches or pull requests