Duolingo error [bug]

[Okabeh]

Describe the bug

Duolingo worked in the evening (November 18th) and the next day it gave this particular error.

Not sure what I means, I tried reinstalling it within Live Container but same error occurred;

Instructions to reproduce

1. Install Duolingo
2. Play it for an hour
3. Retry next day and it probably will not work

What version of LiveContainer are you using?

3.0.0

Other info

No response

[hugeBlack]

This error message generally means that the signature of duolingo is invalid. If you are not using the latest build, You may need to renew jitless cert, or turn off IgnoreAltCertificate.p12. I would recommend to update to the latest build.

If you are using the latest build i.e. 5d43a31, then please refresh apps in your Store.

[Okabeh]

This error message generally means that the signature of duolingo is invalid. If you are not using the latest build, You may need to renew jitless cert, or turn off IgnoreAltCertificate.p12. I would recommend to update to the latest build.

If you are using the latest build i.e. 5d43a31, then please refresh apps in your Store.

Thanks, it works! I have one slightly other question (thought I'd ask here instead of opening another thread);

The apps within Live Container keeps resetting all settings every other day. I'm not sure why this is happening. I already have the IgnoreAltCertificate.p12 turned on to avoid re-logging continuously (the accounts stay logged in but all settings are back to default) but this keeps happening.

Do you perhaps have an idea as to why this happens?

[hugeBlack]

Can‘t confirm. I have not experienced my apps in LiveContainer losing their configs. Are you using google apps like Google Drive? If so, they have sideload detection and will automatically logout when restart.

[Okabeh]

Can‘t confirm. I have not experienced my apps in LiveContainer losing their configs. Are you using google apps like Google Drive? If so, they have sideload detection and will automatically logout when restart.

Mostly with Apollo and Instagram

[hugeBlack]

Then this should be a bug then, I might need to alter my NSUserDefaults handling code to solve this, maybe in next build.