When using the simulator in the Actions Console, I get the response:
"Since your voice wasn’t recognized, I can’t do that right now. Check the Voice Match settings in the Google Home app."
The account under which I am developing has no devices registered, intentionally. This account is used specifically and only for development.
Why does the simulator respond like this, and how can I fix it? The account has no "Google Home app".
I have another (personal) account which I've used to develop the Action initially. The simulator works fine there. Now I'm trying to move the development to an "official" corporate account, and the simulator fails completely.
I can confirm I'm getting exactly the same occurrence here.
Doesn't matter what device type is selected as being used.
Similarly was working fine a couple of days ago.
Looks like Google has broken something with account linking and the Actions on Google Simulator.
I did however read somewhere that best practice you should be delivering some functionality that does not require account linking. That way you will still get explore ratings from users who visit your assistant but refuse to sign in.
However that doesn't fix the core issue of testing functionality that requires sign-in using Actions console simulator.
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.
This question is similar to someone elses. But my phone says untrusted app developer. I click cancel, and by the way I am using ios10, and I go to settings to where there should be trust. but there isn't. it is replaced by verify apps. I click verify apps, and the apps still come up unverified. one app I used was tutuapp.vip, what should I do so I can get back on my apps?
May sound like a child but I am 14, and play games and I'm taking an early start of creating one for a future job of mine.
Apple has this thing where if you download a game or an app from an untrusted developer, they have the option to resign the app. This means that apple is forcing you to not to open the application. Apple usually only resigns apps that are illegal (e.g. Getting paid apps for free, emulators, etc.)This means that you cannot get your data back, and you are forced to either start over, or to legally download the apps on apples app store.
Sorry, there is no way to get your apps back.
I bought few iBeacons today and started playing with ios SDK.
I read in one of the apple forum that we can build and distribute a Apple Passbook pass to users and it can show notification to user when it detects a specific iBeacon.(https://discussions.apple.com/thread/6028034?tstart=0) This feature don't need any app to be installed on the user mobile device. Is this a correct info?
I have been searching the web for exact reference and unfortunately cant find anything very specific to this except sites like passkit.com who promises to build such passbook pass and distribute for you, but since its paid can't try.
Any help/info/reference will be really helpful which can help be build from scratch.
TIA.
Yes, it is possible to send a notification about a Passbook pass to an iOS user when they come near a beacon. They do not need a special app to do this (just the Passbook app, which is pre-installed). The user, however, does need to have installed the pass just like any other Passbook pass.
This works by embedding beacon identifier information in the pass itself. When the Passbook app installs the pass. It starts looking for that beacon in the background. When the device comes across it, the Passbook app sends a notification to the user.
My colleague wrote a detailed blog post about how to do this here. No payment required!
My client needs to find a way to automatically push app updates to a number of iphone 3gs devices remotely. These devices will be in guided access mode so the users will only be able to access the app in question.
I believe we have two option for distribution:
B2B custom app via the Volume Purchase Program
In-house app released with the Apple Enterprise Program
Having researched our options I can see that over the air app updates can be achieved by either:
Building an in-app update functionality to check for new updates (Enterprise only I am guessing?) and automatically update and restart the app
Using an MDM such as http://www.air-watch.com/ (as I understand Apple Configurator must have devices plugged in via USB to work?)
I am wondering if anyone can tell me whether either of those options are possible with the devices being in guided access mode?
Or are there any other solutions, which I have missed, that can automatically manage the app remotely while the device is in guided access mode?
You can solve this with an Enterprise distributed app.
App only. Update check for an OTA-Update from your app when the app is coming to the foreground (or some other metric at your clients leisure, like added time delay, etc). Basically self explanatory; you implement a call to your clients/your API to check the version and inform the user of a new one. The update can either be optional or mandatory (preferably announced by the API and changed when needed); present the user with an alert about it. The user acts upon it and you OTA install via an ITMS link provided by your API call. And that's it.
MDM. Tbh, I'm a bit on shaky ground here. Theoretically this is all possible via MDM too, however I am not sure if it is the (varying) MDM solutions or some misconfigurations, but clients usually seem to lose control after some time.
Both. Yes, you can perfectly well live with both. MDM while everything is fine, and as a backup a well structured App+API mechanism to push the OTA updates out. This is especially useful if you have customers where some departments are under MDM and others are not. So, some may get it via MDM (and if all else fails via the App itself), the rest will get it via the App.
The tradeoffs are a matter of personal preference, if there is a fully working MDM solution in place the update will be pushed out and the user however 'malicious' can do nothing against it. But the same is true for the 'App only' solution, as you have the option to not let him use the app if he does not update (either by not providing a cancel button or, as you are in an enterprise environment and there it is allowed doing an exit(0)).
From experience I prefer any solution that has the 'App only' option as it is the last fallback if anything on client side fails. Whatever may be added on top is just sugar to the cake.
While not strictly relevant, the 'App only' solution always goes well with Push Notifications when an update came out.
I’ve recently downloaded an installed Icenium Graphite (free for 30 days) on my Windows 7, 64 bit. I’ve created a new project (Cross-Platform Device Application jQueryMobile).
My iPhone is plugged in and I can see my device in the Devices panel at the bottom of the IDE.
When I Run-->On device, I obtain an error which basically tells me that I don’t have any provisions.
After several searches, articles and youtube videos, I still can’t get my head around this.
I’ve logged into the apple developer center. It appears I need to enroll and pay 99$ a year as an individual.
If my plan is to eventually publish my application to the Apple Store than I understand the 99$/year fee but if my goal is to simply test locally on my iPhone how can I do this without enrolling?
Is it even possible or the 99$/year is a must regardless if I only plan on testing locally?
If anyone could help me shed some light on this that would be great!
Sincerely
PS: My iPhone is not jailbroken so I can’t use the approaches found in some articles I’ve read.
You can use Icenium Ion to run your app on your iPhone without the need of provision. You can get it from here - https://itunes.apple.com/en/app/icenium-ion/id527547398?mt=8 Also, you don't need to jailbreak your phone to use the app.
What you need to do is the following:
Run Graphite, open your project, connect your device, verify that Graphite recognizes it and fire up Ion on your mobile device. Your app should be loaded automatically. Also, check if in Graphite Ion LiveSync is enabled for your device.
You can check docs.icenium.com for even more details.
Hope that helps.