[Bug]: Cannot login; HTML different error with Lycee Nelson Mandela PRONOTE
c9lypso opened this issue · comments
Description du bug
First of all, awesome app! PRONOTE horribly sucks and it was about time an alternative client got developed.
Unfortunately, Papillon fails to sign in on Nelson Mandela high school's PRONOTE.
Tried both with the GPS method and manual URL method, with or without appending /pronote/eleve.html
.
It returns the error:
Page html is different than expected. Be sure that pronote_url is the direct url to your pronote page.
The login screen shows that it uses "aucun ENT", so no school service; this should be true? This high school, being located in PACA, uses Atrium-Sud as its online school service, but its PRONOTE is separated from it (no option to login from Atrium).
I can still login to the official PRONOTE client.
Etapes à reproduire
- Start Papillon
- Tap the PRONOTE option
- Select "LYCEE NELSON MANDELA" (URL shown is
https://0134003f.index-education.net/pronote
); can be found with zip code 13012. - Input PRONOTE credentials
- Login fails with error "Page html is different than expected".
Comportement attendu
Login should succeed and lead me to the beautiful UI I was expecting ;(
Appareil
Samsung Galaxy A71 (4G)
Système d`exploitation
OneUI 5.1/Android 13
Version
5.7.0 (Play Store)
Environnement
Application native Android
Service scolaire
🦋 Pronote
Captures d'écran / vidéo
No response
Contexte supplémentaire
My PRONOTE account will probably be deleted soon as I stopped using the service, so I might not help in the very near future.
Also, I can write french but chose not to here.
Hello, after checking the link, there is effectively a difference between your Pronote and the html page configured in the api. It's seems like, at the loading, your Pronote is pushing a cookie before reload the page, in scripts, and so the errors displays.
I will check with the staff for a fix, but I didn't know that Pronote integrate that stuff...
After doing some check, it's seems like your etablishment has subscribed to a anti-bot proxy that displays a different html, interpreted in the navigator with the scripts (that's the api didn't do) to display the pronote html. And for this reason, it is not certain that we can find a solution. We'll let you know when we have news, and thank you for the report.