I have been updating the FacebookAPI classes which we have over at Xojo Developer’s Spot to support the recent changes in the Facebook API v2.4, and so far, the code works flawlessly on Linux and Windows. Mac OSX on the other-hand seems to be having an issue loading Facebook altogether. (I suspect it’s my system). At first I believed the issue to be within the framework somewhere, then I tried WebKit, and then tried Safari. For some odd reason, NO secure website (HTTPS) EXCEPT Google and Apple, will load?!?!? So I tried FireFox and a sleuth of other browsers available for Mac, to find that they had no issue whatsoever loading Facebook, or any of the associated domains via HTTPS. Everything was fine with Safari before the last OS update. So, neither the Native, nor Webkit HTMLViewer on my system presently load any needed secure site.
If someone would be willing to test the most recent update to the FacebookAPI-v2.4 demo, I’d be grateful. The Facebook app is the Xojo Developer’s Spot Demo App. All that is really needed is to run the demo, click login, and see if the authentication window even loads; you may dabble around all you want with the API’s if you desire. If you create your own Facebook app through the developer portal, you’ll need to configure the app (in Facebook) and test the demo using your own appID. Alas, that part is explained step by step in the docs not included. This is only the project demo file.
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000010
VM Regions Near 0x10:
–>
__TEXT 0000000000001000-00000000001e5000 [ 1936K] r-x/rwx SM=COW /Users/USER/Downloads/FacebookAPI.debug.app/Contents/MacOS/FacebookAPI.debug
Thanks a million Maximilian! Dang! A nasty WebKit bug in the Xojo framework. Will try switching to Native and see if the bug still appears… Thanks for testing! Apple has yet to reply with a solution for my Safari not loading properly after updating the OS; a search in the apple forums yielded I’m one of a couple thousand, so I don’t feel so alone.
I updated the download source link with the Native Apple HTMLViewer if you wouldn’t mind testing again. If that one works as intended, guess I’ll post a bug report with Xojo for WebKit.
I’ll have to check. That I’m not sure of; although it would be foolish of Xojo to put Native and Webkit as an option in the Mac Inspector if it wasn’t available without being at least greyed for the platform in use. (I understand for “cross-platform” reasons…although it’s very vague for the primarily Windows users).
Update:Apparently the Xojo native (webkit falls back to native) is the only Mac option available…
Guess it’s just a really big Xojo framework bug then. At least it doesn’t plague Web Edition
The authentication window code is as follows:
htmlPane.LoadURL(theurl)
on DocumentComplete
the appToken is retrieved,
and if it’s found, the window is closed.
So you experience a crash (Xojo framework issue), whereas my htmlviewer just remains blank (Mac issue). The deaf, leading the blind
[quote=205800:@Matthew Combatti]I’ll have to check. That I’m not sure of; although it would be foolish of Xojo to put Native and Webkit as an option in the Mac Inspector if it wasn’t available.
[/quote]
The layout editor is used to layout things cross platform
So at the time you design it you cant say definitively that it is / will be ONLY for Windows Linux or OS X since compiling for any of those targets may be selected AFTER you layout the window
[quote=205803:@Norman Palardy]The layout editor is used to layout things cross platform
So at the time you design it you cant say definitively that it is / will be ONLY for Windows Linux or OS X since compiling for any of those targets may be selected AFTER you layout the window[/quote]
Ah! ok I’ll forward you a copy of the source Norman. Perhaps you can verify or dismiss the bug.
