cancel
Showing results for 
Search instead for 
Did you mean: 

Review claims OAuth page doesn't work

AussieDeveloper
Community Member

We're trying to get our cloud-to-cloud integration accepted.

For the past few attempts we keep on failing with a message from the testers:

"Action name `APP_NAME` has been launch , can found on GHA but still failed to load Oauth page. The action has been deprecated again."

We have tested the alpha version of the app on the following phones:

 

Google Pixel 4
Google Pixel 6
Google Pixel 7 
Samsung S8
Samsung S9
Samsung S10
Samsung S23
iPhone 14 Max Pro
iPhone 14
iPhone 13
iPhone 8S
 
In alpha, the oauth page works for all these devices, has always worked for us, it is not very complex - we return a simple html page with a small amount of css to centre the text, there is no javascript.
 
The server logs claim no requests were made to the oauth webpage for the past week.
 
We keep on making little changes to the html page in the hope that it works, but it's been 3 weeks now and we're running out of ideas.
 
Does anyone know how Google tests the integrations, is it an emulator, because recently we found the emulator crashes regularly when launching the chrome webview and we had to increase the memory from 1.5GB to 2GB to get any, not just our oauth pages to show.
2 Recommended AnswerS

sipriyadarshi
Solutions Expert
Solutions Expert
  • In order to test your integration your app should be able to pass the test suite fully. You can refer to the following link to get an understanding as to how the launch process works on Smart Homes .
  • There are many automated test frameworks on iOS and Android like Appium and Selenium to test your applications.

View Recommended Answer in original post

Thanks for the reply, but I don't think you know what you are talking about.

  • We do pass the test suite fully - but that only tests the backend.
  • The Google Testers are claiming that our oauth page is blank, when viewed from their Google Home App, running on their device. They can say this without providing any information - when I asked them for evidence/screenshots/logs or examples as to how they tested the app, so we can reproduce the issue and fix. They suggested I post here and I have.
  • There is no evidence on our cloud function logs of anybody accessing the oauth page during the time we submitted the integration and it was being tested.
  • When we perform extensive testing, on emulators and real hardware and we never get a blank oauth page.
  • We have, however found an issue that on a API 33 Google Play Emulator, default settings, the chrome webview will crash the first time it is used, chrome is asking for permission to save web history, if this is how they are testing our integration then the "blank" oauth is not our fault.
  • I was not aware that you can use an automated test framework on apps you do not control like GHA - can you share documentation on how to do this?

 

View Recommended Answer in original post

3 REPLIES 3

sipriyadarshi
Solutions Expert
Solutions Expert
  • In order to test your integration your app should be able to pass the test suite fully. You can refer to the following link to get an understanding as to how the launch process works on Smart Homes .
  • There are many automated test frameworks on iOS and Android like Appium and Selenium to test your applications.

Thanks for the reply, but I don't think you know what you are talking about.

  • We do pass the test suite fully - but that only tests the backend.
  • The Google Testers are claiming that our oauth page is blank, when viewed from their Google Home App, running on their device. They can say this without providing any information - when I asked them for evidence/screenshots/logs or examples as to how they tested the app, so we can reproduce the issue and fix. They suggested I post here and I have.
  • There is no evidence on our cloud function logs of anybody accessing the oauth page during the time we submitted the integration and it was being tested.
  • When we perform extensive testing, on emulators and real hardware and we never get a blank oauth page.
  • We have, however found an issue that on a API 33 Google Play Emulator, default settings, the chrome webview will crash the first time it is used, chrome is asking for permission to save web history, if this is how they are testing our integration then the "blank" oauth is not our fault.
  • I was not aware that you can use an automated test framework on apps you do not control like GHA - can you share documentation on how to do this?

 

Good news - my Actions were finally passed without any changes on my end.