How to scroll in WebAuthenticationBroker? - windows-8

I am creating a Windows 8 app. I want user to login with LinkedIn. I am using WebAuthenticationBroker for that. But it's not showing the authorization dialog correctly. The "Allow Access" button remains hide and due to unavailability of scroll-bar one can't scroll.
I also tried Windows 8/RT WebAuthenticationBroker view issue - Alternative. It uses WebView and provides better view, but it's useless for me because it's not returning me the authorization code i.e. OAuth response.
According to Tim Heuer it's not possible to customize the WebAuthenticationBroker and I suspect there's issues in LinkedIn dialog itself.
Anyone has idea how to solve my problem?

Windows 8/RT WebAuthenticationBroker view issue - Alternative worked for me. I had issues in callback URL.

Related

Firebase Authentication Sign in Providers Not Enabling

I'm getting started with Firebase and I want to enable one of the authentication services, but the little slider won't turn on.
I'm assuming maybe I'm missing some information but it doesn't tell me anything.
They just recently revamped their entire setup... anyone else struggling to enable any of these?
Success. The slider UI component only works as a button. I was dragging it repeatedly and it wouldn't snap on. Probably a bug. Funny.

xcode twitter api authorize screen issue

I have an app that I'm using the xcode IDE and writing in Objective-C that uses the twitter api and the 'default' twitter login page for username and password.
I already have all the oauth stuff set up and it is working fine.
I create a new view controller with a web view inside it, and pass the URL of https://api.twitter.com/oauth/authorize.
If I put in my email and password, everything works fine - the view disappears, and we are then off and running.
If I press cancel on the twitter login screen, I get a twitter page saying I need to log in. I need to capture the cancel in my code so I can dismiss the view controller, but I cannot find out what the name of the callback is? I tried didFailLoadWithError but that is not it.
Can someone shed some light on this please?
It turns out it can be handled from the same callback that handles a 'correct' login. except looking for a failure.
So, they have handled it correctly within the original callback.

Facebook library login dialog how to modify its appearance?

Using the facebook library in order to login I call this method:
+ (BOOL)openActiveSessionWithReadPermissions:(NSArray*)readPermissions
allowLoginUI:(BOOL)allowLoginUI
completionHandler:(FBSessionStateHandler)handler;
If the allowLoginUI:(BOOL)allowLoginUI parameter is set to yes the facebook login dialog is shown in full screen. Is there any way to change that and have the login dialog appear not in full screen? I would like it to just appear on foreground and take most of the screen size but not full screen.
I've seen this done but I would like to know if it is possible with the current facebook library?
I do not believe you are allowed to modify the login UI. I have seen devs getting rejected for modifying other aspects of the facebook SDK UI bundle (namely the login button) but this was clearly not acceptable.
My best guess is to set allowUI to no, and sort of mimic your own interface.
Although, from a UX perspective, I would prefer you kept it in the style defined by the FB SDK.

UIWebView disable location prompt

Is it possible to disable the location prompt (or auto decline/accept it) that pops up when you visit certain websites that ask for locations? I am not using a MKMapView because my app will be not be just viewing maps (it just may visit websites that might have maps on it).
I'm guessing since the prompt is not being controlled by my app, but by the iOS system, I probably will not be able to auto decline/accept the dialog.
As far as disabling the prompt from within an IOS app while loading a UIWebView, it is possible.
You will need to intercept the html before it gets loaded into the UIWebView then find which part of it triggers the GPS/Location Prompt. Once you found it, you simply remove it from the html then feed the html into the UIWebView thus 'disabling' the prompt. However, as a result, the webpage will be missing that element.
No, it's not possible to do that. Not with UIWebView, not with any iOS browser.
I know no way to prevent the prompt, I hope it will be implemented as a property of the UIWebView.
The dialog is not there for the safety of the user, when it comes to UIWebViews. The app containing the view has already asked for locations access, and it can be enabled and disabled on settings. To ask for location access both from the app and from the web view, I would regard as a bug.

Facebook Page Tab app not appearing to non-page admin users

I am experiencing a problem similar to 2 others who have recently written about this issue.
A newly created Page Tab Facebook app displays for admin users but not for regular users.
I only have 8 page tabs currently so it cannot be that there are too many.
Also, sandbox mode is disabled ( have tried both enabled and disabled).
Can anyone think of a reason that this might be occurring?
I added the tab with the code:
http://www.facebook.com/dialog/pagetab?app_id=YOUR_APP_ID&next=YOUR_URL
Could it have something to do with https in the url as opposed to http?
I am at a loss and do not know how to go about solving this issue.
Any ideas, however far-out they may be,would be aprreciated.
Thank you to anyone who might think they can help...
Have you forgotten to take the app out of Sandbox Mode? (try toggling it just in case, even if it's not in sandbox mode, as this is by far the most likely explanation here)
Also, check there aren't demographic restrictions set on the app or page via the API, as in this case only the users that meet the restrictions will see the tab. (though the admins will always see it)
Also check that you've configured the Page Tab URL and Secure Page Tab URL settings for the app correctly, as if a user uses HTTPS and the App doesn't support it they won't see the tab
If the tab isn't appearing at all it's almost certainly one of those two problems ,if it's displaying but the content isn't rendering, also check your code and make sure it's not fataling on checking the signed_request for non-admins or something like that