The source of this problem is the fact that facebook IDs are not unique; they are app-specific. Each user can have 2 facebook IDs, one for web and one for native.
A suboptimal solution: search for the creator's quests by name instead of facebook ID, effectively treating names as unique.
A better but more difficult solution: take this into account by redesigning the db schema to store both a web_facebook_id and a native_facebook_id.
Another possibility: remove the "created quests" button from the native app and hope that the redundant entries in the user table don't present a problem elsewhere.
Fixed this issue by creating a business account on Facebook, associating all 3 apps with it (web, native, & dev), and then using the Business Mapping API to set the native user ID to be the web user ID.
The source of this problem is the fact that facebook IDs are not unique; they are app-specific. Each user can have 2 facebook IDs, one for web and one for native.
A suboptimal solution: search for the creator's quests by name instead of facebook ID, effectively treating names as unique.
A better but more difficult solution: take this into account by redesigning the db schema to store both a web_facebook_id and a native_facebook_id.
Another possibility: remove the "created quests" button from the native app and hope that the redundant entries in the user table don't present a problem elsewhere.