-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Loads, then goes to white #5
Comments
Yes, the client and API version have been updated. Client to 7.2.0, API to 14, see the new release instructions. |
No that was me who said they had updated. This is an issue after it worked. Now it caches everything, then goes to "finishing up" then all white. |
You are right, I get the same. If they changed the API it will require reverse engineering the changes and recompilation I'm affraid. |
That's part of what I'm not getting, as my API doesn't seem to be having any issues, at least it's not reporting anything to be different. |
I've also noticed that. Tried some stuff. But it fails. However, everytime after reverting i'm able to use the new bundle.js for a while. Something that caught my eye today was in bundle.js you have
I've altered the platform parameter on my end just now. but as said, by having reverted, it always works for a while. But i'm also suspicious of the other parameters, i don't believe all thos parameters where submitted in the previous version. |
IIRC, all of those have always been included, as I remember noticing it myself the very first time I learned how to see the API on facebook. With that said, it has been working for me without issues for the last few days. One of the new things I tried was to use a new token. |
If you have it working now, could you please describe the changes you made? |
Only things I did was uninstall, reinstall then change both client and api versions in both documents to 7.2 and 14 |
Change it back to 7.1 and 12. The new version was rolled back. Way to much issues... |
Wow, you're right, they reverted it. It's 7.1.0 and 13 btw |
Goes to white now. Anyone have any idea why?
The text was updated successfully, but these errors were encountered: