Tell me if branch io supports fallback to AppGallery on Huawei devices without Google Play services? Now on such a device, a browser opens for me, and redirects to Google Play page of my app. Device - Huawei P40 Lite E Android 10.
By documentation branch io supports such market: https://help.branch.io/using-branch/docs/creating-a-deep-link#default-link-behavior
But there isn't any property to configure such function on branch io dashboard.
How can I check fallbacks on Huawei devices? How do I configure this functionality?
Here is my configuration:
I recommend using App Linking. The Unified Linking function allows you to configure links on the AppGallery and Google Play details pages at the same time. Different phones can automatically switch to the corresponding app store.
https://developer.huawei.com/consumer/en/doc/development/AppGallery-connect-Guides/agc-applinking-unifiedlinking-0000001070790553
There is Branch io support answer:
Thank you for contacting Branch Support.
Branch links will open the default app store on the device. On devices
where Huawei App Gallery is the default app store it will be opened to
download the app.
If you want to try opening the Huwaei app market even when there is a
different default app store, you can try entering the App link in the
format https://appmarket://details?id=com.xx.xx
Once the app is installed there is no change in the functionality due
to the source of app install.
UPD 08.02.2021 second answer:
They are two methods on how to use a single link which works on both
Google Play Store and Huawei App Gallery
Method 1 -
Set the Custom URL to point to your app on the Huawei App Gallery, on
the Configuration page. And set the $android_url parameter for all
links to the app on Google Play Store.
In this case on Huawei devices the link will redirect the users to the
Huawei App Gallery when the app is not installed. And on other Android
devices as the link will not be available, the fallback url set by
$android_url will kick in, opening the Google Play Store.
Method 2 -
Choose your app from the Google Play Store on the Configuration page.
If you have any specific links targeting Huawei users, then change the
Default Redirect for those links to the Web URL of your app on the
Huawei App Gallery.
Do let me know if this helps.
UPD 09.02.2021
On the link kindly use the Default Redirect for Android as well.
The default in this case would be the Huawei App Gallery link to your
app.
On the link data page can you add key - $fallback_url
value - The play store link to your app
After making the changes on the link, please test the link on both
Android and Huawei devices at least after an hour or two as the link
level changes sometimes take a while to reflect.
UPD 07.04.2021
We had another round of discussion with the Product team on this
issue, and they mentioned that the fallback to Huawei app gallery is
not supported anymore.
They have not provided us with the exact details, but they seem to
have been changes on the OS level on Huawei devices which has broken
the functionality and which we have been unable to fix due to certain
limitations.
Unfortunately this flow is not supported at the moment.
I do apologise for any impact this might have on your link, but it
does look like we do not have any solutions for this matter at the
moment.
You can refer to the following:
The typical link format of the application details page on Huawei AppGallery is:
https://appgallery.cloud.huawei.com/appDetail? pkgName=packagename&channelId=channelid&referrer=referrer&detailType=0&calltype=AGDLINK
Parameter description:
Packagename: required, the package name to be popularized and applied, such as com.huawei.gamebox ..
Channelid: It is recommended to fill in. To improve the channel identification degree of data analysis, it is recommended to fill in the designated identification number for each channel. If it is not filled in, the system will automatically read the package name of the source media, but the package name cannot be obtained by jumping through the webpage or offline QR code.
Referrer: not required; if not, it will be blank by default. This parameter refers to the secondary channel number. When links are posted on multiple pages (scenes) of the same media, the specific location effect of the media can be identified by the secondary channel number.
DetailType=0&calltype=AGDLINK: basic parameter, which cannot be deleted.
Related
At my company we use Google Play's internal app sharing links to provide builds to QA. As of an hour or so ago, opening any link now fails, showing this error inside Google Play:
To view this content, install and set up a web browsing app.
This happens on every device & OS tested, all of which previously handled links perfectly.
We are not using opt-in testing, only 1 google account is whitelisted for the builds.
The links are in the format https://play.google.com/apps/test/xxxxx/xxxx-xxxx_xxxx.
Since it happened on all devices at the same time, I suspect it's a remote config switch.
Is there any known workaround?
Note: None of these suggested solutions work, as they just let you open the URL in the browser. That doesn't help, as the URL just provides a link to open it in the Play Store.
Try directly this if link is originated from an app for Android to handle:
market://details?id=<package_name>
Note: There's no domain and host.
It was caused by a temporary outage on Google's end. It resolved itself a few hours later.
Use case: send email to users that currently don’t have the app installed. The email shall contain two links for Google (Android devices) and Apple (for iPhone). When the user taps on the link, launch Google play or Apple store app on the phone pointing to the app so that the user can download.
Is this functionality be implemented by Firebase Dynamic Links? We support Android KitKat and above. What is the minimum OS the user will need?
Sai, the use-case you describing is the reason why Firebase Dynamic Links exists. It does not matter how you get your link to the hands of the customers/users. You can use FDL in emails, SMS, iMessage, Facebook, Twiter etc.
You do not need to specify two links. One Firebase Dynamic Link will work on both Android and iOS. If App is not installed, the link will navigate to AppStore or PlayStore. If App is installed, the link will open the App with deep link.
If opened on desktop, the link will navigate to deep link itself. Also check out "dfl" Desktop fallback link parameter for desktop behavior.
Firebase Dynamic Links on Android supported Ice Cream Sandwich and newer. KitKat is supported by FDL.
I uploaded the app on play store but after uploading it shows this app is not compatible with your device. I know it is related with some permissions i used in the app but Is there any way to detect that the app we are going to upload on playstore will not compatible with perticular device.
And how can i raise the ticket on playstore for the same issue.
When you upload an APK to the Play Store (note, you don't actually have to push it to production), there will be a list of devices your app supports.
To see this, select the "APK" tab on the left, then there will be a section titled "Supported devices", which has a link to "See List" - this will let you see which devices your app supports (says I support over 9000 devices).
If the device you expect is not there, you need to make changes to your app (in the manifest), and not open a case with the Play Store (ie. it is something you need to fix, not them)
It is not permission issue. There can be several reasons:
1) your app has in app purchises, and in your country they are not supported (linke in my contry)
2) maybe there are some features, that your device doesn't support, but your app uses, for example : call functionality and your app uses call function.
Hope this helps
We are adding Android Auto and iOS CarPlay support to the existing Android/iOS versions of an app. We are able to successfully test the Auto application using the Android Media Browser simulator as directed by the Android developer documentation.
We also have a stereo head unit that supports both Auto and CarPlay. We are able to use the CarPlay app successfully on the head unit, and we are able to use published Auto apps on the head unit. However, we can't see our development app on the actual device.
The Auto documentation is still a little bit thin, but I'm gathering based on some wording I've seen that Auto apps get some special flag (or similar) added by Google Play when they pass review:
Before making the app available to Android Auto users, Google Play
submits your app for review against the Auto App Quality criteria and
notifies you of the result. If your app is approved, Google Play makes
that app available to Android Auto users.
Based on this, is at all possible to run Auto apps on hardware before they've already been published and approved through Google Play?
This seems like a frustrating chicken-and-egg problem. We'd like to have the confidence that things look good on actual hardware and on target devices before publishing.
It is now possible to test your Android Auto apps on Auto-enabled head units. The procedure is to upload your app to the Play Store in an alpha channel, which you can then install to your device and test in a car. You will even receive feedback from the Auto review team for your app. [Wayne Piekarski]
Follow this
You can also install the Desktop Head Unit (DHU) to test it in software before submitting it to the Play Store. I used this method to make sure most of the quality issues were resolved with my app before submitting it. The DHU does not require the apk to be signed by Google.
Also, submitting it through the store usually takes several hours before you can test. The DHU is, obviously, immediate feedback.
Here's the link: https://developer.android.com/training/auto/testing/index.html
The short answer is no, you can not. It is due to the driver safety review. It will not be able to run on the real device until the app is approved.
But I think, you can contact Google and they can do something about it, if you really need to test it in your car.
We have a fleet tracking Android app which is isntalled on around 100 mobiles.
Problem is to update each mobile whenever there is a patch release. And unfotunately we have not set auto-update.
Now we need to call each driver and follow the process of update from google play.
This is becoming very tedious as they have to go to google play, search the application and install/update it.
And the mobiles are located all over the country.
Before it was easy as Goolge play was giving an option to know the apps installed on each mobile.
Need your advice on how do we manage/automate this update issue.
Build an in-app push notification that there's a new version and have an easy link to Google Play from it. However, this does have a bootstrapping problem, and you will have to make everyone install the new version manually (as in you call them and ask them to do it) at least once. Still, this is your only viable option, as Google Play developer agreement prohibits pushing app updates through other channels.
If you have email or IM contact with the drivers, you can also send them a message there's a new version with the direct link to the Google Play. They will have to open it on their device, of course.
The link format should be market://details?id=com.mycompany.myapp, https://play.google.com/store/apps/details?id=com.mycompany.myapp, or http://market.android.com/details?id=id=com.mycompany.myapp. Either of these three in general should work, though some OEMs have messed up their devices configuration and prevent Google Play app from intercepting the http/https form properly.
You could check a text file located on a server or something like that and then lookup if the current instaleld version is the same as the server version. If not you could download the new apk and open it. As far as I know this is not allowed by Google Play so you must remove the app from google play