enter image description here
Login with google is working and logging in but this loop starts when i don't want to login how can i stop it.
It happens because you use RoundedLoadingButton package. But if you want to stop it when you have an error you can call googleController.stop();
I use keycloak to reset a user's password through a custom flow.
The flow works for resetting the password and logging/auditing error events.
But the context.success() doesn't log events in EVENT_ENTITY. I tried changing the event type to try and find the root cause using
context.getEvent().event(EventType.SEND_RESET_PASSWORD_ERROR); // for eg. context.success();
I am not sure what the problem is, or fail to understand what is different from setting a success and error.
I found the issue and it was me missing a call to send the event on success.
on error on context.getEvent().error(..) which call EventBuilder.send() internally. I had to use context.getEvent().sucess() to save the event on success.
I have a mobile application which works by making sequential calls to different APIs depending upon the action the user is taking. For example,
1) get app specific details go to url https://config.url with GET
2) user login, go to url https://login.url with POST
3)perform step 1 at url https://step.url with POST
4) perform step 2 at url https://step.url with POST
5) get file at url http://file.url with GET
steps (1) and (2) must complete successfully before the remaining steps can execute. How do I stop the current sequence if a mandatory step fails, without affecting other sequential tasks in operation?
I have login scenario in which when the user click on the signin button then the next activity is opened in which there is a list. i am new to appium and find it hard how to get the validation that the login is successfull.
I didnt got success with the below
driver.switchTo().window((String)driver.getWindowHandles().toArray()[windowIndex]);
please guide how to get the current activity & move to awaiting activity, so that i can validate the object existance.
Can you just share the screenshot of the next activity and while launching your apk file with the starting activity name , there is no further need to specify the next activity names. Appium will run the next concurrent activitiesby itself.
I am trying to implement in-app purchase for my Windows Store App (Metro App). I was referring to the code samples here, but when I triggered the RequestProductPurchaseAsync method nothing happens.
When I say nothing happens, it means literally nothing. No return results (the result was supposed to be a receipt since I passed in true for includeReceipt). Also, when I re-checked the ProductLicences[string].IsActive flag it will always return me false.
How do I test this out properly? Thanks a lot!
Make sure the app LicenseInformation.IsTrial is false, otherwise it won't work. In-app product purchases require that the app not be in trial. In a published app, the user would see an error stating that you can't do in-app product purchases under trial license. The simulator doesn't show this warning in the in-app purchase simulation dialog during testing.
You can either modify the initial state of the simulation (see the samples for how to do that) or call RequestAppPurchaseAsync(false) during the simulation run to get a full license for the app, then try the product purchase.
We experienced and solved a similar problem.
Using CurrentAppSimulator worked fine, but bringing up the real purchasing UI with CurrentApp did not.
In a production setting await CurrentApp.RequestProductPurchaseAsync(string,bool) seemed to never return (more specifically, it only returns once after the user has logged in -- subsequent calls did not return).
Additionally, after we tried to bring up the purchasing UI in our app, other applications using the purchasing UI had the same problem -- UI never shows.
Here is the problem code:
private async void CommandInvokedHandler(IUICommand command)
{
switch (command.Label)
{
case "Continue":
licenseInformation = CurrentApp.LicenseInformation;
if (!licenseInformation.ProductLicenses[Notes.ProductName].IsActive)
{
try
{
await CurrentApp.RequestProductPurchaseAsync(Notes.ProductName, false);
// The code never steps over
}
The somewhat-obvious problem with the code above is that the request to bring up the in-app purchase UI is made from within a modal dialog box command handler. The request hangs -- never returns. The not-so-obvious part is that it also blocks all subsequent requests from our application and every other application (until the user's session is restarted).
Upon moving the "try" block out of the command handler, and ensuring that there are no modal UI calls contesting the purchase request, purchasing worked without issue.
EDIT: You should restart (or re-login) to test this. Once the purchasing UI breaks, it will not show until you restart or re-login.
There is a small nuance to follow: to be able to purchase anything using CurrentAppSimulator one needs to call CurrentAppSimulator.RequestAppPurchaseAsync before making any purchase requests. After the operation returned by the call is done, you can successfully call CurrentAppSimulator.RequestProductPurchaseAsync (unless the IsTrial value in LicenseInformation element is set to false in the xml).