Google provides the tools (App Actions Test Tool and App links assistant) for testing intents using Android Studio at the development stage.
But there is a question: can I test app integration with Google Assistant at the closed beta stage (before app release at the Google Play): voice commands, receiving intents and etc.?
For example: at the tests using the App Actions Test Tool and App links assistant deep links and BIIs work fine. Next, I want to test these features at the "real-life case" using Google Assistant and my app from the closed beta. Is this possible?
P.S.: I'm especially interested in "Open app feature" intent
Apps published to any distribution channel in the Play store should have usable app actions for the users that are able to download them. This is something you should be able to test for yourself pretty easily.
Related
I have 2 problems with integration of shortcut's capabilities (but the shortcuts themselves work properly) in Android:
Assistant doesn't see my debug application on phrase "Open myappname"
Assistant doesn't see any shortcut capability which I added to the dynamic shortcuts.
If I clearly understand it will be able after publication at the Google Play, but my application is not designed for this store. How can I force Google Assistant to understand my queries?
For app actions, your application needs to be uploaded to the Google Play Store. That being said, it doesn't need to be published to everyone. At the very least you can create an internal or closed test release.
I developed an application with react-native and I add app actions to the application.
I followed instructions on docs and test the app by App Action Test Tools (AATT) and it worked pretty well (the invocation name is 'Test app').
After creating the preview for actions, I tried with google voice assistant directly (not just using AATT) and still it worked pretty well.
Right now I create a project in google play console with name 'MyApp' and create an Internal testing release and add another user as a tester and upload aab file for this release.
Finally I shared the google play link with tester user.
Tester user installed the app but actions doesn't work with google voice assistant!! I tried different commands, such as 'Hey google, search time in My App' and 'Hey google, search time in Test App' and etc. But non of them worked!
Do I need 'create preview' for Internal testing?
This step is not clear to me, what I need to do more to be sure the app will work with voice assistant without create preview by AATT?
In the past we were able to deploy private versions of our app to EMM's (e.g. VMWare, MobileIron) and test out managed configurations. But today, we are unable to test new app updates within a managed environment.
Android https://developer.android.com/work/managed-configurations
With new Google updates EMMs are no longer able to upload private versions of our app if the app package id conflicts with a publicly available app on Google Play. For regulatory reasons we are unable to just change the package id and test because it is technically not testing the same binaries. Best we can do now is simulate a managed environment using Test DCP : https://play.google.com/store/apps/details?id=com.afwsamples.testdpc
Is this the best we can test without publicly releasing the app update to Google Play? We have contacted VMWare and basically got the same answer but would like a confirmation. Uploading the app to a closed testing track on Google Play and then trying to importing to EMM did not work either.
iOS https://www.appconfig.org/ios/
Basically the same issue for iOS. Apple has kind of removed the Enterprise Developer Account which we previously used to sign and upload our own versions to EMM. The new eligibility requirements are too much. Alternatively, none of the EMMs work with TestFlight. And for iOS we do not know of any app like Android Test DCP to simulate a managed environment. I read a few github chains and Apple forums where companies are just releasing the app publicly then testing to make sure everything works. That can't be right, right?
In the Huawei Store, we could publish an app upgrade via "Version/Upgrade" menu. But once we publish it will directly appear in the store.
Is there any way to publish an app on the Huawei developer console for testing like Beta/Alpha texting in the Google Play console?
Yes. AppGallery Console provides Open testing feature for developers to publish their APK to selected users before releasing it for all. The Opening Testing service is still in beta state. To launch an open test, you should send an email for the application. You can follow the this official link to apply for an Open Test.
You can try HMS Cloud Testing which provides a complete set of automatic test processes based on real mobile phone use. It tests automatically the compatibility, stability, performance, and power consumption of Android apps, without manual intervention.
Please refer the following articles for details.
A Novice Journey towards Cloud Testing - Part I
A Novice Journey towards Cloud Testing - Part II
Cloud Testing: - Variety of tests on your Android App
I have integrated App Indexing and i tested my implementation by
Link Testing in Android Studio , Android Debug Bridge and Deep link testing tool . In all three tests I am able to open the app . But still when i do search in google I am NOT able to see my app with website link like below image.However if app is installed in device I am able to see app in choice of search autocompletion.I have not published the updated version of app in play store.Is that the reason i can't see app with website link?I am confused whether App Indexing is correctly impemented.
The app must be published on Google Play. Then you can use Preview your APK on Search Console.
Also, Declare a website association. After you make association, Google automatically starts indexing any existing or new URLs to your app.
Cheers,
MB