In my native android app i have a "more apps" button which I want to link to all my apps on google play.
I'm following this link: http://developer.android.com/distribute/tools/promote/linking.html#UriSummary
As per the documentation in the link above, i used this query: market://search?q=pub:publisher_name. For publisher name i used my name without the brackets. BUT when i run the app and click on the "more apps" button, the google play store app opens and shows this message:
No results found for "pub:my_name_here"
If i remove the "pub" the url like this:market://search?q=publisher_name
then it shows all my apps. But the problem is that along with my apps, other apps are also being shown which match my surname. Not sure how to resolve this. All i want is to link to only my apps on google play.
I tried searching on Google, StackOverflow but did not find the solution. I tested this on Galaxy Note II. Not sure if it is a device specific issue. Has anyone come across something like this? Thanks!
Just to add to this, I also had this issue and found that adding quotation marks around my developer name solved it.
Instead of this:
Intent intent = new Intent(Intent.ACTION_VIEW, Uri.parse("market://search?q=pub:Liam Cottle"));
Change it to this:
Intent intent = new Intent(Intent.ACTION_VIEW, Uri.parse("market://search?q=pub:\"Liam Cottle\""));
The Google Play store app will only show results which match the quoted name exactly... Well, that's what I found anyway.
We have the same issue and the old link used to work up until now.
The workaround so far is to use
Intent marketIntent = new Intent(Intent.ACTION_VIEW,Uri.parse("http://play.google.com/store/search?q=Vendor+Name"));
startActivity(marketIntent);
This works, but this is triggering the open with window and it also requires us to update every single app.
Edit: The provided answer by Liam does not work as this is the exact link and quotation we have been using for years, which just recently stopped working, the only working solution is using the web link above.
Related
So I have a mobile web that would try to open my android app, if it does not exist, it would fall back to google play.
for chrome, i use this intent:
intent://some_data_sent_to_app#Intent;scheme=app_scheme;package=package_name;end
and it works fine,
now I want to send some referrer string to google play for the INSTALL_REFERRER in an app.
I tried the following link, it has no problem of sending data to google play, but it would not try to open the app
intent://some_data_sent_to_app#Intent;scheme=app_scheme;package=package_name&referrer=referrer_string;end
I wonder what is the correct way to open the app and fall back to google play with the referrer data being passed?
Looks like it can be done by passing S.market_referrer=referrer_string
For example
intent://some_data_sent_to_app#Intent;scheme=app_scheme;package=package_name;S.market_referrer=referrer_string;end
I have not tested this, but there are some check-ins in the chromium repo for this, don't know if it is available in the current version of chrome.
https://codereview.chromium.org/2061493002
This is a known issue that I am working with the team to get fixed. Someone in the past suggested that you can use intent://some_data_sent_to_app#Intent;scheme=app_scheme;package=package_name&referrer=referrer_string;end however the logic of this has never worked specifically because the Chrome browser (and Android Browser) look for a package id that is direct copy of the string which is parsed as package_name&referrer=referrer_string.
With the new scheme, you can pass arguments as extras to the App, but you must encode the URI as follow:
Do Whatever
source
I am building an android app which needs to share some content (image + text) to Facebook, using facebookDialog. The dialog works perfectly when using a Facebook developer account, but when using a regular account, the dialog appears and then disappears instantly. I have tried passing FORCE_DIALOG_AUTH, as i have seen in some similar posts, but in the best case it just keeps the dialog opened a couple more seconds. Code is pretty straight-forward:
FacebookDialog shareDialog = new FacebookDialog.ShareDialogBuilder(getActivity())
.setLink("https://developers.facebook.com /android").setDescription("a description")
.setPicture(mPlant.default_document().getServerImagePath())
.build();
LE: it looks like the dialog only works with the developer account which generated the app id, the problem is with any other fb account
Thanks in advance
> hope this image makes it clear that unless you make this app live you
> cannot test it from other account.
> There are solutions to add tester
> accounts if you want to test it from any other account instead of developer account,
> then in "Roles" tab add a tester account,then test
> through this account.
Please provide error log so that it's easy to find your bug. But while using Facebook SDK in your app, you need to follow a few procedures:
Register your app on Facebook. After registering you will get a Facebook ID.
After that you need to provide your apps package name and class name in which you are using Facebook.
You need to add your hash key to the Facebook setting page.
Found the answer. It needed Facebook app to be updated. strange thing at least they could have propagated correct message that could have save our time.
I tried restarting my `phone but didn't work. I tried same source code on different 'phone and everything started working. I have no clue on what's wrong in the phone that I was working with.
Hope this could help someone.
I want to enable users to share a URL+ text with a WhatsApp group. I want this to work both from iPhones and Androids. However my app is in a browser (it's a website). I'm currently looking into 2 options, but both have issues:
1) The first potential solution - sharing directly from the browser.
I checked out WhatsApp's URL schema and used the following URL to share through my app:
"whatsapp://send?text=Hello%2C%20World!"
However there were several problems with this approach:
It seems to work only with iPhones and not with Androids. Is there a comparable solution somewhere for Androids?
It enables to choose who to send to only after you are redirected to WhatsApp, unless you know the address book ID (=abid) of the user. First, I do not know how to access the abid of users? Second, I am trying to send to a group, in which case there is no abid (right?), and therefore it seems impossible to do this. Is that true?
Also, what happens for Android apps? What is the comparable to the abid, for a group, and how do I get it?
2) The second potential solution - creating a native app which is identical with the browser-based app, but this specific part (where we do the "sharing") is native.
However, it seems to me that in this case I have very similar problems to the ones described above:
I can see how to do this for iOS on WhatsApp's website (see the link above). However, does the WhatsApp URL schema work with Android native apps as well?
Again, the address book ID issue is the same. How do I get it? It may be easier to get the abid on iOS given that we are now a native app, but does it exist for a group? And how about the Android app? Would this share to WhatsApp group work there?
Sharing directly from the browser works both in iPhone and Android if you use WhatsApp version 2.11 or higher. As you said it DIDN'T USED TO work in Android.
U can use the same URL
"whatsapp://send?text=Hello%2C%20World!"
Knowing abid is not possible as far as I know.
Hope this was helpful.
Thank You.
in Android you can invite friends from an app using Intent, see the following Code
final ComponentName name = new ComponentName("com.whatsapp", "com.whatsapp.ContactPicker");
Intent oShareIntent = new Intent();
oShareIntent.setComponent(name);
oShareIntent.setType("text/plain");
oShareIntent.putExtra(android.content.Intent.EXTRA_TEXT, "Your Message");
startActivity(oShareIntent);
I hope this solves your problem
I am trying to open the Android Market in my application's details page.
I am using the following code:
Intent intent = new Intent(Intent.ACTION_VIEW);
intent.setData(Uri.parse("market://details?id=my.app.package"));
startActivity(intent);
However, it seems like this does not work in some devices.
Has anyone experienced a similar issue?
According to the documentation, it seems like the Market application filters out applications based on several criteria:
"filtering might also depend on the country and carrier, the presence or absence of a SIM card, and other factors." http://developer.android.com/guide/appendix/market-filters.html
Probably your application is being filtered out by one of those factors.
One of the best ways to confirm this is to login with your google account in the web market, go to the details page, then try to install the application.
You'll get a message similar to "Your operator is not supported"
Long things short: If im testing my In-App-Billing apk in the market i always receive "RequestPurchase: RESULT_ITEM_UNAVAILABLE"
Im feeling like a complete idiot atm and ran out of ideas how to fix it.
i call mBillingService.requestPurchase("itemxx", ""), wich works fine with static test.purchased.
But as soon as i upload the signed apk as a draft to the android market it doesnt manage to find my predefined item. Mybe the proper Question at this point is: "How does the ID of the Item in the Market has to be "named" relating to the id you made up in your application.
Can anyone provide me with a hint on what else i can try or look up?
APP: itemxx -> Market: itemxx
APP: itemxx -> Market: package.name.itemxx
APP: package.name.itemxx -> Market: package.name.itemxx
APP: package.name.itemxx -> Market: itemxx
I solved the Problem for me. I use the Sample Code from this resource:
http://www.anddev.org/advanced-tutorials-f21/simple-inapp-billing-payment-t52060.html, thanks for that Mr. #Blundell.
Besides changing the Package-Name to get it up and running it turned out that the ID in the app and in the Market has just to be the same, simple as that.
So i call BillingHelper.requestPurchase(mContext, "item.hacke");
and create an Item for the Application in Android market with the ID item.hacke.
Take care of the following Steps:
Enter the Correct Public Key
Use a different gmail account for your tests than the publisher account and enter the mail address as Test-Account right below the PublicKey
Make sure the item in the market is published. Only the Item not the App.
good luck :D