[TIMOB-3150] Facebook Module in RC1 mobile - FBDialog like option needed
| GitHub Issue | n/a |
|---|---|
| Type | Bug |
| Priority | Medium |
| Status | Closed |
| Resolution | Duplicate |
| Resolution Date | 2012-07-26T16:39:36.000+0000 |
| Affected Version/s | n/a |
| Fix Version/s | n/a |
| Components | iOS |
| Labels | n/a |
| Reporter | hamii |
| Assignee | Neeraj Gupta |
| Created | 2011-04-15T03:38:05.000+0000 |
| Updated | 2012-07-26T20:23:58.000+0000 |
Description
The current implementation as I see it down in the objective c code, only allows for a non Safari option when a non multi-tasking enabled device calls into the module. What about when a device has been locked down, by restricting Safari, thus removing it from the device? The Facebook module should detect this at least, or should enable the app to specify that the authenticate method should use a webview, or FBDialog like interface. Webviews are not restricted when Safari has been. The have no url input area and so are restricted to some degree. Parents want to restrict the ability of the device to browse to inappropriate web sites. This is very common with apps with a target audience of younger teens and pre-teens.
Has this been tested in the wild? The new code tries launching facebook, then tries launching Safari, then tries the dialog. Key here is that if the safari launch fails due to parental controls, the app knows and flows through to the dialog.
Duplicate of the problem described by TIMOB-3149.