This isn't a facebook issue at all. Facebook just exhibits this behavior, like many others.
Really, you need to be able to run against the different versions of you app using your custom domain. Think cookies; you cannot access cookies on other domains. You cannot test "real world" behavior if you have to test on a different domain, than the ones you actual deploy on. On Thu, Feb 25, 2010 at 1:28 PM, vivpuri <[email protected]> wrote: > First, it is a facebook issue > Second, you can create a tmp facebook app for testing that points to > the versioned appengine app. Still debugging for existing users is a > pain. It would be better that facebook let you point app to a sandbox > server/url > > Vivek > > On Feb 25, 4:12 pm, Waleed Abdulla <[email protected]> wrote: >> It's a good issue to raise, but shouldn't that be raised to Facebook >> instead? They need to allow running FB Connect apps on more than one >> domain. >> >> Waleed >> >> On Thu, Feb 25, 2010 at 11:15 AM, Jeff Schnitzer <[email protected]>wrote: >> >> >> >> > If you are currently developing a Facebook Connect app or plan to >> > develop a Facebook Connect app, please star this issue: >> >> >http://code.google.com/p/googleappengine/issues/detail?id=2878 >> >> > If you haven't noticed, you soon will: You cannot test your FB >> > Connect app using XX.latest.example.appspot.com. FB Connect requires >> > that you specify a single domain for your application (example.com) >> > and all other domains (example.appspot.com) fail. This makes it >> > impossible to simply deploy a new version of your code and run it >> > against your live data. >> >> > The requested feature: Please allow us to run XX.latest versions on >> > our custom domains. >> > Example: XX.latest.example.com >> >> > Like me, you're probably testing in dev mode with an alternate FB app >> > key, crossing your fingers, and hoping it works when real users touch >> > your new code. Or maybe you dare to test in vivo with your alternate >> > app key, but things don't work quite the same because the live data >> > contains users who haven't authorized your alternate app key. Like >> > me, you've probably exposed real-world users to bugs because you can >> > only test against live data by deploying it to the default domain. >> >> > Please star the issue. >> >> > Thanks, >> > Jeff >> >> > -- >> > You received this message because you are subscribed to the Google Groups >> > "Google App Engine" group. >> > To post to this group, send email to [email protected]. >> > To unsubscribe from this group, send email to >> > [email protected]<google-appengine%2Bunsubscrib >> > [email protected]> >> > . >> > For more options, visit this group at >> >http://groups.google.com/group/google-appengine?hl=en. > > -- > You received this message because you are subscribed to the Google Groups > "Google App Engine" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/google-appengine?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
