I'm currently developing an action with Dialogflow.
As my development is stable enough to be tested, I released it as an Alpha Release and also shared it with some alpha testers.
Since the beginning, I released 10 (alpha) versions: new intents, account linking integration, but mainly Directory information changes, with a nice logo, description, privacy policy and so on...
My problem
Most of my alpha testers don't have access to the latest released version.
Actually they all have access to different (random?) previous versions of my action.
Even following the provided Opt-in link doesn't display the same version of the action (different Directory information).
I'm getting crazy, I tried removing everyone, published a new version, added all my testers back again... but it didn't help.
I think there's something I didn't get about Alpha Release...
Thanks for your help.
An additional question: do the testers have to click the Opt-in link, or should they be able to invoke my action from their Google Assistant app as soon as they're added as testers ?
Partial answer... I don't know about the different alpha versions but I can answer your question about the Opt-in link...
My limited experience tells me they need to accept the Opt-in link. When an alpha-tester tried invoking my Action prior to accepting the Opt-in link, they just got "related" web results. Immediately after accepting the Opt-in, they were able to invoke my action from their Google Assistant.
Related
I wonder how to make my application (which is already published on play-store and app-store) updates automatically when a new version is released.
I have found some packages that support similar thing like: https://pub.dev/packages/new_version and https://pub.dev/packages/upgrader but the issue is that all these packages display a dialog when a new version is detected. But I am asking about making it completely automatic without any dialogs appearing.
I also knew about https://pub.dev/packages/firebase_remote_config but it doesn't answer my question about releasing new version.
I see this feature in a lot of apps but I don't know how it's made in flutter.
Unfortunately you can't auto-update.
Auto-update strategy depends on user settings
You can only ask user for update
It is not possible that the Application gets automatically downloaded and installed. Both ways are also not allowed from the AppStore and PlayStore Agreements.
I use only Admob to serve ads on my iOS apps made with Unity. I don't want to display AppTrackingTransparency prompt since most users would reply to NOT be tracked.
I would like to:
keep using Admob
not using IFDA but only the new SKADNetwork
In short, I want my app to serve ads as if the user answered NO the to ATT prompt (since this is what's going to happen anyway)
How do I accomplish this with Unity?
Is it enough to use the following code?
AdRequest request = new AdRequest.Builder()
.AddExtra("npa", "1")
.Build();
If I use the above code, can I fill the App Privacy Section stating that my apps are not tracking users?
In the the following page:
https://developers.google.com/admob/ios/ios14
I can read:
"If you decide to include App Tracking Transparency (ATT) in your app..."
So according to Google, including ATT is an option... how exactly do I choose not to include it AND keep using Admob?
This is a pretty actual topic now since iOS 14.5 release. Let's sort some things out to proceed:
According to the updated Apple Terms and Conditions, you must show ATT popup to the users who use iOS 14.5. This is an Apple requirement with which I would not recommend to trick;
If your app uses any of the Ad Network and doesn't show an ATT popup, you will be rejected on the App Review stage when you try to release an update. You really have a small chance to be lucky and pass it, but most probably you'll not;
If the user blocks tracking, it doesn't mean you'll not show ads and lose money. Just to be clear: you are allowed to show ads even if a user blocks the tracking. You just need to use Ad Network API/SDK accordingly to not pass the device’s advertising identifier.
To support an ATT status with AdMob in Unity, you need to use an AdMob plugin for Unity of version at least 5.4.0. I'm attaching a link on official releases on GitHub with description and usage samples:
AdMob plugin releases for Unity.
In summary: consider not ignoring the Apple requirements, because it will directly affect your app. They always check your app manually before each release and track how your app meets their requirements, especially now, in the first week of iOS 14.5 public release.
I have deployed a flutter app on the google play as a production mode, which is this link, https://play.google.com/store/apps/details?id=yurikanamba.lovealapp
(sorry the social login doesn't work now)
I can see the latest update from the link, like screenshots, but I can still see the word (beta) right next to the app name like this.
I sent this link to some of my friends, but they cannot see the (beta) like I do.
Do you know why I can see that and how to get rid of the (beta) right next to the app name?
I guess I should disable the Beta project in our App releases on google console, but there is nothing I can deactivate my beta release...
I have got the same problem:
First I published my app as a public beta version then I released it to production track. However, when using my developer profile I'm still seeing this Beta title.
I have a tried to unregister from testers list, then cleared my browser cache (desktop and mobile), my Google cache but I'm still seeing it.
Try this anyway, it might work for you.
The only solution I found is to use another account that was not listed as beta tester, but it seems that for profiles who have been (or still are) beta testers, "Beta" won't go away from your app title.
I had a serious bug in my itunes latest updated build. I want to restrict users to update the current version. How?
any suggestions will help me a lot.
do you mean you want people who have the buggy version to update ?
unless you have push notifications setup with your app, or a means to display them a message, or have their emails as part of a sign up process, your very limited to what you can do.
If you have published the new version, just make it clear in the version notes that this includes a bug fix.
Currently, there is no functionality built into the App Store to force updates.
In your initial version, you should add a way to force updates, and then test to ensure that it works. Typically, you will have a callback to the server and a way to display a message and link them to the update in the store.
If you don't have such functionality, and you are making any API calls, you can add a version number to the API call, and if the version isn't sent, then you can refuse access, and preferably send them a message.
My employer has a free iOS app in iTunesConnect that was originally released a couple of years ago and has received various updates over time. They now wish to stop supporting older versions of the application (1.x) and disable these older versions of the app.
My questions are:
Can we stop users from re-installing old versions of the app? If yes, how?
How do we disable/remove old versions of the app in iTunesConnect?
What is Apple's policy regarding disabling/removing old versions of applications?
I'm not an iOS developer and am unfamiliar with the whole Apple application development process. I have searched the web as well as the Apple developer centre and I've read through the Apple Developer Program Terms and Conditions but I haven't been able to find answers to any of my questions.
I have managed to find information about removing an application from sale but this removes the entire application, rather than just specific versions. (Deleting a free app from iTunesConnect)
David Smith's article (http://david-smith.org/blog/2012/06/20/hacking-paid-upgrades/) on Paid Upgrades mentions the ability to provide fixes for previous versions if they're not deleted from iTunesConnect. When I log into iTunesConnect, I only see the current version of the app listed so I'm assuming prior versions have been deleted already. I would, however, like to confirm that users can no longer download old versions of the app.
This article mentions users being able to download old versions of apps from iCloud (http://www.macrumors.com/2011/06/09/icloud-supports-re-downloading-some-discontinued-apps/) - can we prevent this? One option would be to mark the the version as having a "legal issue" but what ramifications does this have? and if I can't see the app in iTunesConnect then how do I do it?
I found a post asking about how to force a user to upgrade the application every time a new version is released but this doesn't answer my questions either. We want the users to upgrade but we're not wanting to force it programmatically. (Can I force an iPhone user to upgrade an application?)
I've also found lots of posts asking how to revert to previous versions of an app in the app store but again, this is not what we're wanting to do. We're wanting to disable older versions of the app but leave the most recent versions alone.
Before the flame wars begin:
Users that are unable to update to the latest version of the app for whatever reason are able to use a mobile website in place of the app. The website has the exact same functionality.
Can answers please be kept on-topic rather than getting into great debates over whether one should/shouldn't maintain legacy versions.
Thanks in advance :)
Users can typically only ever download the latest version of an application. There are a few ways I think they can get around that but in general only the latest version is available to users via the normal means.
If, however, you absolutely must prevent the old versions from being released you can do so when submitting a new update. Right after you say "Ready for Upload" you will be asked a question about if this update was for a 'legal reason' if you click YES then you will be given the opportunity to disable old versions of the app from download.
As to Apple's policy on this...I have no idea. But I can't think of any policy that would require you to support older versions moving forward.