I have deployed an Alpha version of my app and supplied the email address of a tester and received the opt-in link the user can use to access the Alpha app. In typical fashion, Google gives no instructions for the user, who clicks on the link and promptly gets an error message that no Google or Stackflow search throws any light on.
A further Stackflow search reveals a complex procedure for an Android phone involving copying the opt-in link to Google Notes, pressing on it, and then taking the option to open the Google Assistant app. It would be difficult to find a better way to discourage testers.
Also, this only opens the app on an Android phone. No mention of how the 20 testers can access the Alpha app on Google Home or Nest Mini. Frustrating when the app is specifically designed for use on Google Home or Nest Mini and not on a phone. Does anyone have a solution?
Users need to opt-in to the alpha program on the phone by following the link. (They shouldn't need to copy it, but they will likely need to open it in an actual browser such as chrome.)
Once they have opted in, however, it will be usable on any device linked to the same account on your approved list and that they used to accept.
Related
I am trying to test an alpha version of a dialogflow/google-actions on my Android phone, but Google Assistant don't open the opt-in link as expected (see screenshot below).
What I did :
I have created a project in Dialogflow, and activate the Google Assistant option inside Dialogflow
I have configured the associated project on Actions-on-Google
The "Simulator" works well and the "Testing on Device" option is activated
The Alpha release has the "Deployed" status and my gmail email is in the alpha-testers list
But when I click on the opt-in link from my Android phone, it only opens a blank page which ask me to give a feedback on nothing (as shown in the screenshot).
Two additional things to make sure you've done before Alpha testing:
Make sure you have the Google Home app installed on the phone you're testing with and that app is logged into the account you're inviting into Alpha.
Make sure you've allowed enough time - even in the "Deployed" state, it can still take a few hours to be available to everyone.
I'm playing around with api.ai to add some possibilities to google assistant and the google home.
I've created a new project in "Action on google" with some very very simple interactions defined in a new agent in api.ai ( only one intent and a few possible responses)
following those steps: https://developers.google.com/actions/get-started/create-project-agent
I now try to test it on my device. I've first tested it in the simulator following those steps:
https://developers.google.com/actions/get-started/preview-the-app
So I can test it in the simulator by saying "talk to my test app". Unfortunatly I don't kow what to say to my home device to trigger the testing. (Note that my device in setup in FRENCH so it is maybe a language issue)
I've read that :
all you need to do is log into the device using the same account that you used to authorize your action for testing in the simulator. Once you authorize your action for previewing, it will automatically be available on the Google Home device assigned to that same account. Note that you need to be authorized in the API.AI account under the same Google account in order for this to work!
I use only one google account, the same on home device, api.ai and google actions. This account is the owner of the new project when I check its permissions. So this should be fine.
Any idea would be helpful. Thanks
As of today (Oct. 6th 2017), you will be able to set French as a language for your API.ai bot and test it on a device or in the web simulator.
Make sure that you have also configured the related Actions on Google app in English AND French (and eventually for the locales -- french (Europe) and french (Canada)). You must have one configuration per language/locale in your bot.
Unfortunately, while the Google Assistant has launched in French, Actions on Google hasn't yet. Until it does, there is no French support for testing actions except through the simulator (where you'll be testing in a different language).
I have a problem with an iOS App using Vuforia and Unity with a valid Facebook Plugin, the problem comes not in the plugin itself (that works properly), but in the Facebook Review process to make the App public and let all users in.
Today doing tests on the finished app, I realized that when using a valid Facebook Plugin (or any other Facebook implementation) with an user that is not the Facebook User Owner of the app (in this case me), Facebook request you to go to "App Status and Review" to click on:
"Do you want to make this app and all its live features available to the general public? YES| NO". This was traditionally allowed to be clicked, but today it's not. The option is not allowed.
"Yes" would make the app accessible to everybody. But this option (YES) is not available a priori, because the App needs first to pass a Facebook review process, in particular a Facebook Review Process to determine if the App is in agreement with its policy. (So we have to pass two reviews: Apple and then Facebook)
The problem here is apparently it's impossible to a Vuforia-Unity App to pass this process. To pass the Facebook Review process you need to send them your App in one of this two available format:
sending the id to Apple Store App (that is impossible to do, you can not send App Store an unfinished app), or
sending them a file containing a Simulated Build (using Terminal to build the project in xcodebuild -arch i386 simulatorXX).
None of this available options provided by Facebook are possible to Unity-Vuforia, technically, so it's technically impossible to obtain the approval of the App. This is because:
App Store is not going to pass an App that is not working (the FB button won't work, so App Store is not going to allow us finish the process and they will reject). So you cannot provide an AppStore-id to the Facebook Review team.
As far as Facebook only receives "Simulated Builds" it would be impossible to a Vuforia Unity App to be accepted, this is because when you are using Unity + Vuforia you can not build a simulated build, is incompatible. So is impossible to fit this requirement.
My questions here to you to try to solve this are:
Did you have this problem and solved it previously?
Is there anyway to avoid the Facebook review?
Do you know how long does it take to Facebook do the review?
Can you think in anything else to try to solve this?
PS: I am using a Neatplug plugin to connect to Facebook.
I know that apple made the app store to, among other things, discourage web apps and control an unfair 30% cut of app transactions. Luckily for me, my rev comes from companies that are listed on the app, not users.
However, I want an app that does nothing but immediately open default browser and navigate to my webapp page. There is not even intermediary screen - See app icon/name on phone desktop, click, browser with webapp url launches.
Will this have problems getting approved by apple? If so what are the issues that I need to circumvent/overcome, and suggestions to do so? Thanks.
App Store Review Guidelines, 2.12:
Apps that are not very useful, are simply web sites bundled as apps, or do not provide any lasting entertainment value may be rejected
You can essentially do this using the apple-mobile-web-app-capable and apple-touch-icon attributes supported by Safari, and you'll save the $99 fee.
Hi can any one suggest me it is possible or not and if possible then how?
The premise is that the user pays for the app via a website and they gets an access code to send to her guests via the website. The user downloads the free app from the iPhone store and enters the code. We're trying to figure out if we can enable each user to customize the app icon so it can appear with a different image or text on the user phone.
You can't. The application's icon (and the application's property list file) is in the application bundle, which cannot be modified.
This would also violate the iOS SDK Terms of Use and the iTunes Store Terms of Service; you cannot have a third-party receive payment to access a free iOS application.
You can customize the iOS icon of a web app clipping, and put the web site to be clipped behind your private paywall. Apple has been reported in the past to accept App store apps that generate URLs to customized clippable web apps. No idea if they currently or will continue to do so.
Icons on App store iOS apps for stock OS devices can only be changed by Apple approving an update.
Evan is right... This goes against so many terms of the iOS SDK.
One thing you could do (but I can't guarantee it will be accepted by Apple) is create a registration system on your website. Then have a login on the App as soon as it loads and check that the user has a valid account which has paid the subscription. You would have to handle all of your payment stuff on the webside though, meaning the app would be useless unless the user has already sorted that out. If you do this, on submission of your app make sure you provide Apple with a demo account username and password!
As for the icon, you can't change it once the App is submitted. It is bundled in with your app binary and there is also a logo included in iTunes connect. You can change them, but only by submitting a new binary.