I have created an Azure Logic App in the Azure portal and successfully added several steps. I add the Azure DevOps List Iterations step and click the sign-in button. A popup prompts me to sign-in and then closes and I am left with the follow error in the Logic Apps designer:
Failed with error: 'The browser is closed.'. Please sign in again.
I have am recreating a workflow that I originally created using Microsoft Power Automate (Flow) so I know that my credentials should work.
Now when I hit the sign-in again I do not get the option to re-enter any credentials nor change accounts.
What fixed it for me was allowing 3rd party cookies:
In your browser settings, make sure that you allow all cookies (including 3rd party cookies: a lot of Microsoft webapps depend on that),
Refresh the Logic App page (might not be required, but it doesn't hurt),
Add a new connection and sign in.
You can then block 3rd party cookies again after this if you wish.
for me change browser from Chrome to MS Edge beta helped
For this problem, please check the resource group which your logic app belongs to. When you click the "Sign in" first time, it will generate a "API Connection" in the same resource group of you logic app. Its name should be like "visualstudioteamservices" (shown as below screenshot).
Please delete this api connection and then wait a few minutes(because there may be a delay in deleting operation). Then go back to your logic app and delete the DevOps List Iterations action, then create the DevOps List Iterations action again it will ask you for the sign in credential.
By the way, if your browser remember the last credential, it may still have some problem. Please delete the api connection and change to another browser to have a try.
Open an incognito/private window in your browser, then attempt to create the connection.
Just had the exact same issue, thought it had to do with my subscription being free trial.
But it logged in perfectly once I switched from Safari to Chrome (on a MacOS 11.2).
I had the same problem using Firefox to create a Logic App, solved by turning off Enhanced Tracking Protection for portal.azure.com
Related
I want to publish this action but everytime I submit for production it shows the same message for denial. I don't want account linking of any type for my actions. Please help me in this problem.
It seems by mistake you have enabled Account Linking in your action.
If you don't want any kind of authentication or linking in your actions, check Account Linking section under Develop menu and clear it.
If it is linked you will get an option to clear it at the right side of the panel.
If you want Account Linking than you need to provide atleast one login credentials in testing credentials section.
My test invocation name is "Mrs Tang", so i input "Talk to Mrs Tang", but it responds "Sorry, this action is not available in simulation"...
Does anybody know How can I resolve this error?
According to the doc:
Turn on the Web & App Activity, Device Information, and Voice & Audio
Activity permissions on the Activity controls page for your Google
account. You need to do this to use the Actions Simulator, which lets
you test your actions on the web without a hardware device.
And I had do what Jeremy Gordon suggested. To add a second google account in the GCP IAM console with a viewer action permission and then login with this second google account in an incognito window for the web simulator to work.
I had a related problem (I could test with my main developer account, but not my test credentials). I eventually got it working with the non-primary account.
The missing link for me was that when I was viewing the simulator, I was actually signed in to two accounts, my primary google account (developer account, shows up in the main frame of the page, upper right corner), and the account I authorized when 'starting' the simulator (email address shows up in the simulator frame), which was my test credentials. The second test account repeatedly gave me the "Sorry, this action is not supported in simulation" message, until I:
1) Added the test account as a Conversation API Viewer & Client in GCP IAM console
2) Visited the 'create link' (the one that comes up when you click share) in an incognito window, and signed into the secondary account there such that I was signed into only one account in that incognito window.
After that, invocations connected to the app.
Make sure you are logged into the same account you used to deploy the test action and that the deployment has been done within the past half hour or so. If you have not set all the information on the Actions on Google Console, you may need to use the invocation phrase "Talk to my test app".
I think sometimes I run into the same error. I get past it by toggling the Active switch off and on.
Same problem I encountered. You must be logged in via the secondary google account. Do logout from the account and login via the account that is paired with api.ai.
why I can't use google action in web simulator
I got this to work by saying "talk to my test app" or typing it in to the simulator prompt, that triggered my app to start in the simulator.
I had the same problem. I needed to set the location first (it defaults to Google-Headquaters), if you are in some other region (like in germany as i am).
Then go on with "Mit meiner Test-App sprechen" (Talk to my test app), or whatever it is in your language!
I did not get this message on my invocation, but on my my second input:"Sorry, this action is not available for your app.".
It turns out the simulator had left the conversation right after the invocation (and it did mention that in the small print).
This happened because I returned a FinalResponse for the invocation. And a final response is pretty final, it will terminate your conversation.
So, after a FinalResponse you can only get back in your action/conversation by a new invocation or a deep link. If you want to suggest questions/inputs, then you should return ExpectedInputs.
You might need to turn on Web & App Activity to let group members use some Google Assistant features.(if you are using organizational account)
https://support.google.com/assistant/answer/7219584?hl=en
If you are using any organization's Google Accounts then there might be an access issue. So use your own personal Gmail account.
Take a look here, organization's might not be given you access. So use your personal Gmail and follow the Docs, you will able to create your agent/ actions and able to test it with simulator as well as in android device.
At time of testing the Google Action you need to set the location to the country which you selected while developing or submitting your Google Action.
By default US is selected in testing but if your action is for one particular country only then you need to select that. You can see in image the field where you can select location
I am locally testing an app that integrates with Quickbooks IPP. I had connected to a demo account provided by Quickbooks developer program when I signed up but it didn't have enough data so I created my own demo account with a copy of a bunch of good data. I then cleared out the tokens and stuff in my app stored from the other demo account so I could start over. The problem is, now when I try to connect my app to this new qb account (using a different login to Quickbooks), I just keep getting this error:
Oops! An error has occurred.
Please close this window and try again.
Error Code: invalid_database
Message: The application has already been subscribed to by another user for this company
I don't see how anyone could have connected to this local app before, but just in case, I went to the "Manage My Apps" screen and the only thing I see there is "QuickBooks Online".
It is probably not related, but I'm also getting a javascript error message after clicking "Authorize" in the Intuit popup.
Line: 3
Error: Unexpected call to method or property access.
When I attempt to debug the javascript it is code in jQuery but seems to stem from the "notifyDoubleClickOfSalesActivity" function in the "Intuit.DFA.min.js" file.
What can I do at this point? I know my code is good because I was able to connect the first time.
Go to you developer account and disconnect all connected connections. This should clear up the issue.
If not, please submit a support ticket through appcenter.intuit.com.
If you already have a valid access token/connection for a particular company, another user from the same company cannot again authorize access. That is the error you see. If you go into your account on appcenter you can disconnect that IA connection, so you are able to re-create it with another user. Your code can also call the disconnect API to disconnect it, and lastly you can login as the end user and go to your account and disconnect the app.
Jarred
This question already has answers here:
Please login to use the PayPal sandbox feature
(5 answers)
Closed 9 years ago.
DISCLAIMER: This question is specifically for the Paypal forum.
I have two Sandbox test accounts. parijat_kalia#hotmail.com (PERSONAL) and parijat_kalia-facilitator#hotmail.com (BUSINESS). The second one has the API credentials and I am using the NVP API to test our e-commerce subscription plan
. The response I get is :
10501: Invalid Configuration This transaction cannot be processed due to an invalid merchant configuration. Occurs when the billing agreement is disabled or inactive.
Hence, to activate it, I presume I need to log in with this sandbox account into the sandbox website so as to activate the billing agreement. The steps I follow are pretty basic.
Login to developers.paypal.com
Click on Applications tab in the horizontal menu
Click on Sandbox accounts in the vertical menu
Click on the specific accounts 'parijat_kalia-facilitator#hotmail.com' dropdown arrow button.
Click on Sandbox site
When i click on sandbox site, it loads in the PERSONAL account in the email i.e 'parijat_kalia#hotmail.com'. I obviously change this and try to login with the business account credentials. However it does not log me in whatsoever. I have changed the password, literally copy pasted it, but it does not work. Nor does deleting the cookies/clearing the cache and terminating the history help. Also, I am using Chrome, not IE.
Also, I presume this error is with Paypal's sandbox website, since the API call is technically logging me in with the credentials (I infer this since I am getting error 10501).
Can you please tell me what is going wrong?
I had an issue similar to that the other day. I was trying to switch from one developer account to another, but it kept logging me in as the first one. So, I couldn't use any of the sandbox accounts for the 2nd account.
I circumvented this issue by switching to private browsing mode in chrome (ctrl+shift+N) and logging in that way.
I can't guarantee this will fix your issue because it's not the same as mine, but it might help.
Misplacedme's answer worked for me, but I don't have enough rep yet, so I'll reply and add some info.
Chrome: Use an Incognito Window (ctrl+shift+N)
Opera: Use a New Private Window (ctrl+shift+N)
IE: No need for special window. It works as it used to.
Firefox: No need for special window. It works as it used to.
Safari: No need for special window. It works as it used to.
Note: These are all on a Windows 8 PC (sorry, I know most people in their right mind aren't using win8 much less developers)
A program I wrote crashes on startup. (Win XP).
A dialog "Please tell Microsoft about this problem." appears. I want to be told about the problem since it's my app.
Thing is, clicking through (clicking link: 'View the contents of the error report'), the "Error Report Contents" dialog doesn't let my customers copy its contents to the clipboard.
Do you know how a user can get a copy of this report to forward to me, the developer?
Don't worry. The developers can subscribe to WinQual. Microsoft will then forward the error reports to them.
Windows Error Reporting is part of Microsoft's Winqual service.
Sign up at the Winqual web site. Instead of just using a username/password to log in, you'll need to purchase an SSL certificate to identify yourself and your organization. This costs $99 if you only need the cert for identification purposes. If you also want to use it to sign code, it's $499.
Run the Microsoft Product Feedback Mapping Tool (available from the Winqual site) on a local copy of your application, and submit the results to the Winqual web site. This registers your application with Winqual.
From this point forward, any errors reported via Windows Error Reporting against your submitted applications are available to you if you log in to Winqual.
Use Alt-printscreen that grabs a copy of the active window, then paste it into word or something.