I am trying to open the Salesforce home page through UI automation (Testcafe), the Salesforce loading symbol is present for long time.
It was worked previously and Sandbox refresh facing this problem.
Not upgraded the Testcafe but now the code is not working
Related
We are testing on moblie app using Appium, Which feature is to upload a video on Server. After uploading video it will be visible on Dashboard of Website. The dashboard feature is not present in mobile app. So here We need to check that Video related details using Selenium as it is on Website. Any Suggestion? How can we do this without performing separate tests.
This is integration testing so are in effect two different tests/steps.
You could do it in one project though so you could do something like:
open your mobile app using Appium
upload the video
open a browser using webdriver
navigate to the relevant page and check the video uploaded
close the browser
continue testing or close the mobile app
I uploaded an app a react native app on google play console for closed testing. The release was approved and I followed the steps to add testers inside closed testing and send them the join from the android link on their email. One of them was my own for testing.
Whenever I am clicking on the link it is taking an infinite time to load the app. And the app is not going to the download page on the Google play store where it is supposed to take me.
Is this a usual problem does it always takes that much time. Or I am missing anything here.
I trying to use Auth0 in a office add-in (React SPA), specifically Excel.
I am using the popup to login instead of the redirect because the redirect doesn’t load in the iframe.
(The error for the iframe is "Refused to frame because an ancestor violates the following Content Security Policy directive: “frame-ancestors ‘none’” ").
The issue I’m having is once I login successfully, the pop just goes white and gets stuck on the login/callback.
I’ve checked the logs, it says a successful log but it doesn’t say anything about an exchange (success or failure).
I’ve tested the pop up on a different application (react web app) and it works perfectly fine.
The login we are using is the Universal Login (the new one, not the classic)
I’m interested in any and all approaches for using the Universal Login in this context.
Thanks
So there is this Payment provider called World Pay, that enables applications to collect payment information via their own provided template form (https://beta.developer.worldpay.com/docs/wpop/template-form).
A working implementation of this for Angular can be found here:
How to integrate worldpay with angular2
Using this code I’ve managed to get it working for Android (and on the browser), but not on iOS. More specifically on the iOs builds the template form does not load, I just get a blank page.
The error I get in the iOS logs is:
ERROR Internal navigation rejected - <allow-navigation> not set for url='about:blank'
I have added:
<allow-navigation href="https://cdn.worldpay.com/*" />
into the config.xml and it has made no difference.
There is a lot of advise online to not use iframes on Ionic apps and to use the in cordova app browser instead, however I am not sure how to open the a browser page when all I have is the address of a script (https://cdn.worldpay.com/v1/worldpay.js).
Any help would be greatly appreciated.
I have had the facebook connect set up for over a few months and have done a lot of testing on it and everything seems to be working correctly. Suddenly when I try to login using the php facebook sdk I get redirected to the following page https://www.facebook.com/help/258359927634494
It seems to let me login on occasion, but it usually redirects to this page. I assume my app was reported however we only have a few test users at this time as we are in beta and I stopped my app from asking for repeatedly for post permissions a while back as soon as I was aware it was doing that. What can I do to clear up the report?
This message appears when an app loads the login dialog many times in a short duration. Make sure you are only loading the dialog once per user. Until this redirect behavior is tweaked to be me more lenient, try waiting ~30 seconds between tests.