I am using Oauth 2.0 for google sign in. For that, I am using html button for sign in as per https://developers.google.com/+/web/signin/add-button . When I am checking this in chrome/firefox/safari it comes with red button with white text(Since I am using default theme -dark). But IE it appears as blue button with only 'g' not as 'g+'.
Browser Detail:
IE-11 on windows 8.1 - 64bit
This is Google testing different buttons on a subset of visitors. Most of your users will never see the blue button. There is unlikely anything you can do about it.
Related
I am trying to change the display of the following login with keycloak page.
https://imgur.com/a/X18bmgC
This shows up with Safari when starting the app.
The problem I have is that the user has to scroll to see the " New user " part of my WebView. And this is a problem.
I'd like to change the display of my WebView to make it look like this if possible :
https://imgur.com/a/DYfpkRS
Here I had to manually unzoom the page.
<ReactNativeKeycloakProvider
authClient={keycloak}
onEvent={onEvent}
initOptions={{
redirectUri: 'mobile://presentation',
inAppBrowserOptions: {
ephemeralWebSession: true,
modalEnabled: true,
},
}}>
This is the code displaying the Keycloak Login page in Safari ( https://github.com/react-keycloak/react-native-keycloak ).
I've checked the different InAppBrowser options here : https://github.com/proyecto26/react-native-inappbrowser#ios-options
When changing the values of each of these options, I can see no differences on the iPhone I'm using. When I change 'ephemeralWebSession' from true to false, I can see the difference. But every other option makes no difference for me. I tried to change 'modalTransitionStyle', 'modalPresentationStyle', 'readerMode' and 'preferredBarTintColor' values, but nothing shows different on the WebView.
I don't understand what I should change to get my WebView to change aswell.
I realize this is about 6 months old as I'm writing this answer, but I had this same issue and came across this in a search.
There is an open issue with InAppBrowser that addresses this: https://github.com/proyecto26/react-native-inappbrowser/issues/292
In short, RN Keycloak calls the InAppBrowser openAuth method to start an ASWebAuthenticationSession instead of a typical web session with the open method. ASWebAuthenticationSession is not customizable, per Apple.
So, the choice is to modify the RN Keycloak package to use the open method, or to do some overriding trickery with Objective-C as found here: https://msolarana.netlify.app/2021/01/06/fixing-aswebauthenticationsession-presentation/
When I try log in in my application with Facebook, I have page in Safari browser with text: You already have authorization PPFF. Or Are you want to have authorization in PPFF?
Also there is the gear on top of the text instead of the application logo. How I can change gear on my logo and type Application name instead of PPFF?
This has been reported earlier and is by design. This dialog will always show up when you start the login flow for a user that is already logged into your app.
You also can't change the appearance of the dialog unfortunately.
You can find the original report here: https://developers.facebook.com/bugs/1024399197610999/
Thanks.
I've been following Facebook code sample "FBShareSample" to create a share dialog,
The example handles the fallback for user without FB App installed.
Everything is working well with FB App but when I get to the fallback the UI in my app look different from the one in FBDemo (navigation bar, buttons etc.)
In addition the friends button is not active.
Am I missing some kind of configuration in my iOS client? Is it somehting that need to be configured on my App page on FB?
I've used Charles to analyse the request and response and the only difference between FB sample code and my code was the userAgent string.
The problem was resolved by removing from the UserAgent parameter the string: " webView", for some reason this specific string caused FB to return a different layout/CSS page when this parameter was present.
when we click on a link to our site, www.tekiki.com, from inside the twitter iphone client (search for tekiki.com on the twitter mobile client), the site appears in a boxed area.
is this an iframe or something we can break out of? we tried iframe-busting code, but it fails. we suspect this is a uiwebview. if true, can we bust out and open the site in safari/chrome via javascript?
When you click on a link within the official Twitter iOS app, it opens up a new modal view that contains a UIWebView. There is no way that you can break out of this view and into a different app since Twitter controls the experience. iOS only supports fast app switching via registered URL schemes such as fb://1234567890, not via javascript, etc.
The only way would be if they had an additional button that gave the user the option to open the page in a different app.
So I've seen telephone links being treated in 2 different ways on mobile safari on web pages. (on ipad and ipod touch):
1 - On my one page, when I click on the link it just displays a popup saying: "Cannot Open Page. Safari cannot open the page because the address is invalid"
HTML code looks like: 1-555-123-4455 (just an example of what my real number looks like)
Also here I'm using plain HMTL mobile boilerplate as codebase
2 - On another page, when I click on the link, it displays a popup giving the user 2 options, Add to Contacts and Copy.
HTML code looks like: <a data-height-watch="" class="button button-block no-border trackConversion" href="tel:15551234455" style="height: 40px;">Call 1-555-123-4455</a> (another example of the real code)
Runs on Foundation Zurb
Is this something one can control progammatically? If so, how can I make sure the user is met with the 2nd "response"? Does it maybe have to do with Foundation Zurb?
As far as i know this depends on device specifications. Also if you have any third party plugins installed in your device such as skype, then it may work differenty.