I was trying to make an alpha release of my app, the opt-in link that has to be shared with the testers is not opening on the desktop browsers but is working fine when directly opened on the mobile device. I am unable to figure out the problem.
This is working as expected or at least a known issue. The opt-in link is supposed to be opened on mobile devices and not in desktop browsers.
From the Google docs:
The Actions directory for the web is not supported for opt-in to alpha/beta. Make sure your testers follow the link on their mobile devices (Android or iOS).
When users click on this link, they are directed to the corresponding Action's directory page. They should click on the I'm in button at the bottom of the Action's directory page to opt in as a tester for the first time.
Related
My URL is same as below, i will get this link to my mail from sendgrid and in iOS when i tap on this it always loads the browser first (safari most of the case) and opens in app preview page even though app is installed.
URL:<a clicktracking="off" href="https://{project_name}.page.link/?link=https://{project_name}.page.link/users/email_check/{{ $email_token }}&apn=com.{project_name}.app&isi={applestoreid}&ibi=com.{project_name}.app&efr=1">https://{project_name}.page.link/?link=https://{project_name}.page.link/users/email_check/{{ $email_token }}&apn=com.{project_name}.app&isi={applestoreid}&ibi=com.{project_name}.app&efr=1</a>
When you access a dynamic link in a browser. It will intentionally not go to your app because the actions indicate that your intent is to open a web page.
If you have your custom domain from Firebase ie: [your custom domain].app.goo.gl, send it into your link like so:
https://[your custom code].app.goo.gl/
And then tap that link. Does it open the app, or does it go to Safari? If it goes to Safari, it means that you haven't configured your iOS app for universal links yet, which is needed to support opening your custom domain url directly in the app. In Xcode, go to the Capabilities tab, and ensure that you've added the universal link domain as described in Apple's docs.
If you tapped the site address on the far top-right on iOS, it disables universal linking on that iOS app, until you long-tap and ask to open in the app again.
Second, you can't type in universal links into Safari's address bar and navigate to the app. Safari, by design, will open that URL in the browser. The easiest, most reliable way to test whether universal links are working is to put a universal link into the app, and tap the link from there.
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.
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 need to implement facebook login in Adobe AIR app for Desktop/Mobile.
I saw some docs on the code required for this.
My concern is, which platform should be selected in facebook apps console. Is it web ? Then what should be the web urls & where to place them ?
Well if you are building a mobile app, then you might want to select Android or iOS depending on the platform. If you are building the same app for both platforms then select any one of those and later under settings of your app dashboard you can click on Add Platform and add the other one. If your app has a canvas presence then you can add that as well later on. Regardless of what you pick initially, you can always add/edit platforms on your app dashboard.
I'm developing a Facebook app that has a responsive layout. Sometimes my app has to generate a link for the user. Whenever possible, the links will send the user to a Page Tab (when the user is on a desktop) and other times it will link directly to the app (when the user is on a mobile phone).
What is the default behavior for Facebook on tablets? Does it show the mobile site or the desktop site?
Should I use the mobile or desktop version of my app on tablets?
Update: In response to BBog's question in the comments:
My app prefers the desktop version because it includes a Like-gate. If the user experience is good for a tablet to view the app in a page tab (which is only available on www.facebook.com ie non-mobile), then that is preferred because the like button will be displayed at the top of the page, above the app's iframe. In contrast, the mobile version of the app requires that the user click a link that takes them to the (mobile) facebook page which they must like to un-gate the app. It adds an extra step for the user and requires that they navigate away from the app for a moment. Users might be discouraged by this extra step and decide not to enter the gate.
For Android tablets - Honestly, it depends on how you want Facebook to handle it. If you look at the android native app linking wiki - https://developers.facebook.com/docs/mobile/android/deep_linking/, Facebook provides you the option to choose the user experience. The facebook native android app itself treats tablets like mobile phones. It would be ideal if your app is compatible with tablets, and then you can enable deep-linking which will let the user view the content inside of your app.
For iOS, it's handled from within the iOS bundle id.
Unable to find a concrete answer, I ended up detected the user's referral on the first page access. Then if www.facebook.com is in the url, I go to desktop. Otherwise I go to mobile..
if ($detect->isTablet()) {
session_start();
if (!isset($_SESSION["tabletAsMobile"]))
$_SESSION["tabletAsMobile"] = (stripos($_SERVER["HTTP_REFERER"], 'www.facebook.com')===true):'0':'1';
}
$useMobileLinks = ($detect->isMobile() || ($detect->isTablet() && $_SESSION["tabletAsMobile"]));
}