Electron version v14 to v15 update Problem - authentication

I have the following problem and now after several days still can not solve it.
I am upgrading an Electron app from version 12 to version 22. The app is there to make certain data packages of our customer more manageable. I have already managed to update the app to version 22, but there is still an error that occurred when updating from version 14 to version 15.
To log in to the app, the external login page of our customer opens in a second window of the app. The login is handled there. I only get back whether the login was successful or not. Afterwards it is checked if the file packages are up to date or if updates are available ect.
So far, everything works fine. But from version 14 to version 15 of Electron there is a problem. The login works, but the following query for updates ect. fails. This query is only possible if you are logged in.
In the Developer Tools I see that I get redirected from request url to the login page. As far as I understand, the Problem is related to the cookies. As if the query would not have access to the cookies of the successful login. But when I look at the breaking changes of version 15 I don't find anything about it.
Does anyone know what the problem could be or how I could fix it?

Related

Auth0 Lock - We're sorry something went wrong when attempting to log in

I commented this problem on the following thread for an active issue regarding Auth0 lock, but wanted to ask here for more reach in case anyone else has experienced this.
From what I've researched, it seems that many people are having this issue, and it doesn't seem like there's a known explanation to what's going on.
The unfortunate thing is that this is happening to end users, and from what I have seen devs have not been able to reproduce this error.
https://github.com/auth0/lock/issues/1838#issuecomment-918434321
Description
User is able to view our Auth0 Lock
User is not able to successfully sign up
We created an account for them in Auth0 directly and are able to log in using credentials we created for them via the Lock
User is not able to log in using the credentials and is shown the "We're sorry something went wrong when attempting to log in message"
Auth0 logs don't actually show this user's attempts/errors when logging in
Reproduction
Unable to reproduce locally, but trying everything we can to do so, including blocking all cookies (not the problem)
Attempting to get any console warnings from the user as well
Environment
Lock version: 11.30.4
React Version: 17.0.2
Next.js Version: 11.1.0
Chrome 91, Windows

Automatically update Vue site / PWA with new release

I have a Vue app that is used both in the browser and as a PWA. I would like to ensure users receive the latest version whenever updates have been pushed to the server.
I am using Nginx, Django and vue-cli along with #vue/cli-plugin-pwa.
Currently when I npm run build and then push the new version to the server, users get the old version of the app (in browser as well as PWA on their phones). To get the new version they do a hard refresh in the browser or for the PWA they close the app and reopen it again.
Is there a way to ensure a version check is done every time the app is loaded so that the new version is retrieved?
In the end I found this excellent article which covers how to display a notification when an update is available. The user is then able to click the notification which updates the app.
https://dev.to/drbragg/handling-service-worker-updates-in-your-vue-pwa-1pip

Heroku error when attempting to deploy app from dropbox

I am trying to deploy a node app on heroku via the web GUI for dropbox, and I get the error:
Item could not be modified:
"Content-Type" request header must be set to "application/json".
Any clues as to what that might mean?
Disclaimer: I was not the one who wrote the app, just made two mods for heroku.
In case you haven't found an answer... I have the same problem.
You probably need to update your runtime stack.
Here's Heroku's message on their website:
"The legacy Cedar-10 stack has been deprecated and reached its end-of-life on November 4, 2015. Applications may continue running, however you will not be able to push to your application without upgrading to Cedar-14 first."
How to update informations are available here:
https://devcenter.heroku.com/articles/cedar-14-migration#upgrading-the-production-app-to-cedar-14
I have the same problem. I raised a ticket at Heroku. They replied,
"Are you using Firefox? We seen this recently with Firefox and we are currently working on a fix. In the meantime, you can use another browser like Google Chrome for deploying your app."
And using Google Chrome fixes the problem.

OpenERP Apps for more than 3 users

one month before i installed openerp 7 all in one version in windows, i have successfully installed the apps when i have user less then 3 but when i create more users and try to install more app openerp account ask for email and password after that he display following message (An OpenERP Enterprise subscription is required for one-click installation of OpenERP Apps for more than 3 users.)
how to fix this issue please guide me,
i also delete all the user except administrator but same message is displayed. even i deleted the database and restore another database and try to install app but same message is displayed with old database name and same number of users
You just need to sign in with the account you used to download the installation package. The local server will then start downloading the files.
Go to the APPS section of your account to get the download.
Ideally though, you can also set up BZR to do a pull so when there are updates you can get them in relatively easily also.
Well clearly it is a bug in OpenERP v7.
I have created a bug report https://bugs.launchpad.net/openobject-addons/+bug/1260377 fell free to subscribe to it.

March 2013: Paypal Sandbox login loops back to developer page [duplicate]

This question already has answers here:
Please login to use the PayPal sandbox feature
(5 answers)
Closed 9 years ago.
Since Paypal developer changed in March 2013, I've been unable to get into the sandbox.
I logged in to the new developer site OK with my actual Paypal account details.
I managed to import my accounts into the new development site (marked worryingly as 'beta') using the link
"Looking for Sandbox? Import your test accounts to continue testing. Learn what's new."
But clicking the link 'Sandbox site' on any of the accounts results in me being taken to:
This is the link where I'm greeted with a Paypal Sandbox logo and a single link reading "Please log in to use the PayPal Sandbox features."
Clicking on this link takes you back to where you have come from - that is the developer page where I am already logged in.
I did raise a support question with Paypal, but a week has passed and it's gone unanswered, so I'm hoping someone here can tell me what I'm missing in this new version?
I'm unable to reproduce this. I'm logging into my sandbox accounts just fine. I'm also able to test things like Express Checkout without any issue.
I know that browser cache and cookies can often be a big issue on the sandbox. For example, when I first attempted to try this after seeing your post I was getting a Proxy Error when trying to load sandbox.paypal.com. I closed and re-opened my browser, though, and then everything worked as expected. Maybe give that a shot.
As Andrew Angell points out - this crazy behaviour was down to the web browser caching. I just cleared out everything in Chrome (Tools > Clear Browsing Data) and wiped everything since the beginning of time and that's got it. Nice catch, thanks Andrew. Appreciated.
The reason every browser I tried did this, is because I've used them all with Paypal - of course - so hence they all do the same thing, leading you to thing the issue is upstream.
Clear your cache and cookie simply by pressing
CTRL + SHIFT + DELETE for WINDOWS
COMMAND + SHIFT + DELETE for MAC
It works for me.
Clearing doesn't help me with this, USE CHROME INCOGNITO MODE(new window) - it works for me :)