I had made an account on Odesk but when upwork came I made another account there and in the meant time I opened my old odesk account on upwork.
Now I have a project on my old upwork account and today I saw a notification about the video calling verification from the upwork, I quickly disabled my new upwork account and since then I am worried that if I do video call with them, how many chances are there that they won't disable my account for duplication reason?
Any help or suggestion would be appreciated!
Just continue with one account only and disable another account. You are safe!
Related
As a dev I have inherited a Google app that is not verified.
The app was left mid-way through the verification process, and the email thread mentioned on the OAuth consent screen section has long since been deleted (I have access to said admin email address, and it isn't there):
I have looked through google help resources and stack overflow questions such as this:
Comply with domain verification requirements
But I can't seem to find a way to restart or resurrect this email conversation with Google having deleted the original thread. I don't really want to have to delete the existing app and create a new one as there are customers using it (as an unverified app).
Is there a way for me to have the verification emails resent, does anyone know?
For some additional context - I want to reopen the verification conversation to allow only enterprise accounts to use the app, as described here: https://support.google.com/cloud/answer/9110914#enterprise&zippy=%2Cmy-application-has-users-with-enterprise-accounts-from-another-google-workspace-domain-how-does-this-apply-to-my-google-workspace-or-cloud-identity-enterprise-accounts
Thanks in advance
My bad - you just have to go in and edit the app, make any change, and you are prompted that a new email will be sent.
I have an app in sandbox mode and I have a sandbox user that is pending. (It has also been at least a day since the user was added). The user can successfully use my app and has given authorization; however, the user's likes returns an empty response (I know they can only access liked media from other authorized sandbox users, but the user has liked media from my account that is set as the admin). The Instagram API documentation states that the user may go to their developer site and accept/decline sandbox invites from the Sandbox Invites tab except my user is shown the developer register page instead. Does anyone know what is going on/how to fix this?
Instagram made sweeping changes to it's API and the way it is accessed recently. As a result of the lockdown the Sandbox Invite process is glitchy at best. I myself just ran into this issue of invites not showing up.
It seems, for the moment, the only way to access the invite is to fill out the developer form(I just used a http://localhost:8000 URL and a random phone number that is not likely to exist, although try without one as it might not be necessary). That should automatically forward you to the invite page where the invited user can then accept or decline a Sandbox Invite.
It's a bit of a mess and the lack of documentation / indication to indicate that this step is mandatory doesn't help matters. Hope this helps save some time and headaches!
I'm trying to connect my application with Google calendar to receive data. I registered a new application in Google Developers Console, activated Google Calender API and tried to configure the Oauth consent screen.
There I selected my email address, entered a product name and tried to save it.
What it says:
Sorry, there’s a problem. If you entered information, check it and try again. Otherwise, the problem might clear up on its own, so check back later.
What's my mistake here? By Google it is not the best failure description. I also can not find anything else about it in the internet, only that some one suggested to enter a billing account, what I don't want. Any ideas?
I signed out of all Google accounts, signed back in, and then it worked.
I meet the some problem.
I used google cloud with two accounts, i guess there is conflict with two accounts. I clean the chrome browser history and cache , then the problem is solved.
If anyone is here within this last week in 2020, this is a GSuite bug that's being tracked here -
https://issuetracker.google.com/issues/150325704
No one has been able to update or create add-ons. Clearing cache, incognito - none of it has any effect here. Just have to wait for the devs.
True story bros, can't post on meta because I don't have enough rep here. So I ask here, prepared for the flames (of love).
I had a google account that was provided through my college which I have graduated and moved on. The account has been closed and now it appears I can not log into my SO account anymore that was associated with that google account.
Do I have any options to recover it or do I start over and lose my (not so) massive amounts of rep, badges, and the access to my previous Qs and As.
Thanks for the certain kind responses I am sure to get for this question.
Dude, you just find a computer that you have set to log into automatically to your e-mail and haven't since logged out since the expiration of your account. Then the credentials should still be valid for SO.
Once you are logged in here, then you just follow the instructions here and you can add more login credentials to your SO account.
What I am trying to do:
create a test user for testing in app purchase in my app.
What I am doing:
Logging into itunes connect.
Clicking on Manage Users
Clicking on Test User
Filling out the form.
What Error I am getting:
Could not convert Apple ID account to iTunes store account.
Doesnt seem to matter how I fill that form out I keep getting the above error. What am I doing wrong?
If I then try and resubmit the form again i get:
The email address you entered already belongs to an existing Apple account. Please try again.,
However when I look at my users it tells me I dont have any and when I try and use one I created it doesn't let me.
I had accepted all agreements, and apparently time heals all wounds because as of 11/19/2011 its back up and working.
I had this problem today as well. When I went to go create a test user this morning, it would give me the same error. Just a few minutes ago I thought I'd give it another try and when I logged in, I noticed that I needed to accept a new agreement amendment (which I had forgotten to do this morning). After accepting the agreement, I was then able to create a test account without any issues.
I switched Country to United States - and it helped me to fix the issue & to create in-app test user.