[MOD-2318] iOS: Update Facebook iOS-SDK to 4.18.0, fix docs, add new methods
GitHub Issue | n/a |
---|---|
Type | Improvement |
Priority | Medium |
Status | Closed |
Resolution | Fixed |
Resolution Date | 2017-01-10T08:40:02.000+0000 |
Affected Version/s | n/a |
Fix Version/s | Release 6.1.0 |
Components | |
Labels | n/a |
Reporter | Hans Knöchel |
Assignee | Hans Knöchel |
Created | 2016-12-23T20:20:41.000+0000 |
Updated | 2018-08-06T17:49:27.000+0000 |
Description
- Update Facebook iOS-SDK to 4.18.0 - Fix some doc errors - ExposeappID
and currentAccessToken
Comments
- Hans Knöchel 2016-12-23 PR (ti.facebook): https://github.com/appcelerator-modules/ti.facebook/pull/80 PR (titanium_mobile): https://github.com/appcelerator/titanium_mobile/pull/8735
- Abir Mukherjee 2017-05-23 [~hansknoechel] Can you please provide test cases for this ticket?
- Hans Knöchel 2017-05-26
Test-Case:
Expected result: The app does not crash and no error-log is shown. The access-token in this example is invalid and *can* be replaced by a real access-token that may be generated using the Facebook API-Explorer. I do not think it is necessary for this case, since the handling is done internally by Facebook and we don't intercept there, so validating against "no crash" will be fine for this case. Special note: Testing in the Simulator will show thevar fb = require('facebook'); var appID = '517802691665259'; var win = Ti.UI.createWindow({ backgroundColor: '#fff' }); var btn = Ti.UI.createButton({ title: 'Set App-ID and Access-Token' }); btn.addEventListener('click', function() { fb.setAppID(appID); fb.setCurrentAccessToken({ accessToken: 'my-new-token', permissions: ['email'], appID: appID, userID: 'hansknoechel' }); }); win.add(btn); win.open();
Falling back to storing access token in NSUserDefaults because of simulator bug
warning, indicating an Sim-Issue of iOS itself that is logged by the Facebook SDK. This is nothing specific to this PR or Titanium in general. - Eric Merriman 2018-08-06 Cleaning up older fixed issues. If this issue should not have been closed as fixed, please reopen.