Pressing Start on Valkyrie 4.2.1 now shows a "Well that didn't work" error
Browser: Edge 128
Method: Extension
Online store version and language: Desktop/en-us (en-au Store) PSDLE version: 4.2.1 Valkyrie
Problem: When pressing start on the transaction history page, it no longer prompts for a password and works. I receive an error stating "Well, that didn't work Wait a minute and try again."
How to replicate: Go to PS Store transaction history page. PSDLE will show on top of the screen as per normal. Press Start to see error.
At a glance it seems CORS related based on their server config. Basically, either intentionally or by accident, the server providing the Entitlements through the older API is not allowing access to the page(s) PSDLE is running on. It may or may not remedy itself in time.
There's nothing I can really do. Add-ons/extensions that bypass CORS may help but I have none to recommend. ~~As always when there's a new issue I have trouble signing in.~~
Not experiencing any login issues personally. Usually pressing Start takes me to a login page where I have to input my password.
Now however, pressing Start posts the error before getting redirected to the password screen.
Same error me on FireFox.
I just tried to get a new listing of my PS3 download history today, and get this error on both Firefox and Chrome. The same steps as the original post are identical to what I have tried.
Might be time to call it.
4.2.2 released which removes the Transaction History button from the extension popup. The extension will still execute PSDLE Valkyrie as before in the hopes that it comes back, otherwise there's been a X/Close button in the top right corner for a while now so the panel can be used normally.
same issue with 4.2.2
` psdle.valkyrie.js:2115 PSDLE | Ready.
The following strings need to be removed from app/pending-strings.js:
- vt.page.boku.reverify
- vt.request.code
- vt.please.wait
- vt.paypal.doesnt.open.automatically
- vt.button.continue
- vt.card.network.title
checkPendingCollisions @ ?nuDataSessionId=bc2dc1d0-dd8c-11ef-a866-a19fe8f2f389...
Unhandled error in promise: TypeError: Cannot read property 'xxx' of undefined. tryCatcher @ ?nuDataSessionId=bc2dc1d0-dd8c-11ef-a866-a19fe8f2f389...
Fetch failed for resource: localization/en.json fetchI18nResource @ ?nuDataSessionId=bc2dc1d0-dd8c-11ef-a866-a19fe8f2f389...
XHR request failed with status 403 (Forbidden). xhr.onload @ ?nuDataSessionId=bc2dc1d0-dd8c-11ef-a866-a19fe8f2f389...
Promise rejection: Unexpected token < in JSON at position 0. fileReaderReady @ ?nuDataSessionId=bc2dc1d0-dd8c-11ef-a866-a19fe8f2f389... `
My above comment is still relevant, including the ability to dismiss it.
It was left in with the hopes it will come back although that is increasingly unlikely by the day. If you do not need the barebones PS4/5 Library export you can stop using the extension.
What exactly do you mean by barebone library export?
Whatever is available from the Library (Gotham) PSDLE, which is not much. After the initial push to support it I've not gone back to it.
At a glance it seems CORS related based on their server config. Basically, either intentionally or by accident, the server providing the Entitlements through the older API is not allowing access to the page(s) PSDLE is running on. It may or may not remedy itself in time.
There's nothing I can really do. Add-ons/extensions that bypass CORS may help but I have none to recommend. ~As always when there's a new issue I have trouble signing in.~
Doesn't seem like CORS. I've tried with "--disable-web-security" and there was no difference.