Has anyone ever seen the osapi endpoints missing from the request for the
shindig js? I occasionally get back javascript that is missing the endpoints
and all my osapi calls fail (undefined). For example here is a good response
"osapi.services":{"gadgets.rpc":["container.listMethods"],"//%host%/opensocial/rpc":"spaces.update
spaces.delete albums.create http.head gadgets.token
activitystreams.supportedFields messages.modify userprefs.create
activities.create permissions.hasPermission containersecuritytoken.refresh
userprefs.get applications.get http.get spaces.supportedFields
mediaItems.delete spaces.get people.get gadgets.supportedFields
gadgets.cajaSupportedFields mediaItems.update http.put appdata.create
activitystreams.delete http.delete cache.invalidate albums.delete
userprefs.delete applications.create messages.delete appdata.update
people.update activities.supportedFields applications.update http.post
albums.get gadgets.cajole gadgets.proxySupportedFields applications.delete
people.supportedFields gadgets.metadata albums.supportedFields albums.update
spaces.create activities.delete mediaItems.get groups.get
applications.supportedFields mediaItems.supportedFields gadgets.proxy
activities.update gadgetContext.get activitystreams.create activitystreams.get
messages.get activitystreams.update mediaItems.create messages.create
gadgets.jsSupportedFields gadgets.tokenSupportedFields activities.get
gadgets.js appdata.get appdata.delete userprefs.update
system.listMethods".split(" “)}
and a bad one
"osapi.services":{"gadgets.rpc":["container.listMethods”]}
It seems to be a timing issue and MAY have been introduced when I started using
updateContainerSecurityToken refreshing (but I can’t say that for sure — I only
started seeing this when I implemented the refresh logic).
Ideas what to look for?
doug
