I have been using google actions with actions sdk and most of the functionality seems to work. However, I am facing consistent issues across a few alpha test users on the updates to the application.
I notice that the latest deployed to the cloud function is what seems to run on the Simulator but an old version appears when viewing on a phone. For example, the icon that I set in the images directory is just not showing (even after 2 days) on my phone while the latest appears in the Simulator. The same with some images from Cloud storage. I tried clearing the cache and storage from the Assistant app on my android phone. Yet the problem persists.
Is there some setting or disabling of cache that needs to be specified in the NodeJS based client code or in the actions console? Thanks.
Go to the Test tab and click on the Reset Test option, such as in the screenshot. It should work.
Related
I'm trying to add a select channel trait.
what I did was that I followed the docs,
1- Add the ATTRIBUTES to the device I want to apply this feature on, for example, a TV device type
2- I guess we are all done as every other command works with my code
What I actually did was the following to the device database in Firestore
then added the
case "action.devices.commands.selectChannel":
in the
switch (execution.command) {}
code
then reloaded the device from the google home app
then when I try to call
"Change to ABC on my TV"
it says
'Sorry, I don't understand.'
and nothing appears on the logs
otherwise, everything is working perfectly,i.e setting the volume and On/Off.
what am I doing wrong, please?
UPDATE:
Today I tried command "action.devices.commands.returnChannel" and "action.devices.commands.relativeChannel" and they are working fine
and all three commands belongs to the same trait!
I've seen a lot of users complaining about this command on many sites
like the following 1,2,
could this be related,
I'm still in debug mode, would it be fixed when I publish my app
UPDATE #2
I tried it today with an android phone and it works fine with selectChannel command,
previously I was testing with an iPhone with google home and google assistant apps on their latest release, and the selectChannel is the only command that didn't work there.
Hope it's just related to the debugging mode
It is usually unexpected to have a trait / feature working on the Google Home App on Android but not on the iOS version, as their functionality is nearly identical. The accuracy on the speech to text conversion on both platforms might be different, which could be affecting the functionality. You can try out typing your request to see if that helps in any way.
After a tiring 3.5 months I learned how to build and launch an app using Flutter and Android Studio. I tested in debug mode on various emulators and all worked well.
I then built the app bundle and uploaded on to Google Play Store as an internal release - again everything ran well.
I pushed this in to Production. After a week of waiting for a review, the app launched. I uninstalled the test version and installed the live production version - and that's when the problems started. The app began to crash in places it hadn't before. Namely on certain pages (and often after the render of certain pages the app closes after c.3 seconds) or upon button presses on certain pages.
I have now added Crashlytics to the app (which I didn't have before), and have pushed this as a second version on to the Google Play Store - and again it's pending review. The questions I have are:
Can I deactivate an app once it's live on the app store to prevent any more downloads? - Is there any code that can be added to the app to do this internally? I can not see any options or instructions within the Play Store. It seems a little crazy that I now know my app has 'bugs' which never materalised in test, but i can't 'switch it off'?
I have only been able to add Crashlytics this time for a new production release, and once installed and I can try and work out what the problem is with error logs. Once I have I will have to create a third version and again add as a new release and wait for Google to approve - is this really the most efficient way?
Why would or could a Production release of an app crash when the Debug version, or Production release version in Internal Test mode, did not? - I find it so strange that I have so many tools available and yet none detected a problem until launch
Thanks in advance!
you can unpublish your app from playstore
goto console>select your app>setup>advanced setting>unpublish app
this will stop your app from appearing to new users and getting new download from
playstore
2.fixing bugs always need a new release to update your app there is no way to get around
uploading a new release and waiting for the review to end (this is for production app)
3.your testing might not have encountered any bugs because you might be testing on one
device or emulator with a specific api for example api 30 ,and the bugs are being
detected on other apis or device properties you haven't covered in your testing
I'm trying to deploy the app on the google play store, and I was wondering if I did that correctly. I have deployed the app as beta testing last week, and today I just uploaded to google play as production mode. I created new app bundle by running "flutter build appbundle" in my project, and put that generated file into the production track.
So far my google play console is something looks like this
On the picture #3, I can see the rollout history as full rollout, but in side of the production I can also see something says you have a release in produciton that hasn't been rolled out.
Does that mean I just need to wait the app reviewed? or deactivate previous app bundle and do something else?
That looks correct. I just recently deployed an app to Android and it took over a week, maybe 2. I also noticed that that view isn't the most clear and descriptive. If you go to the Dashboard view you'll see all your apps and see the Status column. It'll say Published when it's live.
I have followed the steps given in http://developer.samsung.com/tv/develop/legacy-platform-library/art00121/index, and the application appears on the Smart Hub on the TV. However, when I make some changes in the application, and package it again selecting "Update the packaged files on the server", do a "Apps Sync" and run the application, the updates are not reflected.
I have tried changing the application name and version in config.xml. Only the application name changes in smart hub, but the application when opened is what was installed the first time on the TV.
If a new project is made and the same steps are followed, the new application appears on the smart hub, but an update to it has the same problem.
Am I missing something while packaging the same application for a second time?
Not sure if this is useful but I believe the device seems to cache the files. I had the same issue today and was quite frustrating.
I managed to find two solutions:
1) shut down the device and re-launch again (connect to server and the Apps Sync)
2) when you export the app in the IDE, make sure you name the package name differently + title & description need to be different too.
By doing this, Apps Sync will add another app (so you'll have two of the same app, but just click on the last one that appears in the apps list - hope that makes sense). If you want to remove the apps, simply access the widgetlist.xml which will be in the root of your server and then remove the apps references from there.
I hope that helps.
I am porting an Android app for BlackBerry and during tests I see my saved user data (properties and a list of activities) disapearing each time I upload my newly build BAR to the device.
Will this happen on every update of the app?
On Android, my local data stays permanently on uploading and installing new versions.
I do not want to use shared storage for this data to avoid too many permissions, since the user won't understand why I need this shared storage (user could wonder about if I want to steal his other data).
This seems to be an issue of the Android VM version used at that specific time. In the meantime, the behaviour is as one would expect it, and all user data stays even after app update.