{"action":"opened","issue":{"url":"https://api.github.com/repos/ParsePlatform/parse-server/issues/954","repository_url":"https://api.github.com/repos/ParsePlatform/parse-server","labels_url":"https://api.github.com/repos/ParsePlatform/parse-server/issues/954/labels{/name}","comments_url":"https://api.github.com/repos/ParsePlatform/parse-server/issues/954/comments","events_url":"https://api.github.com/repos/ParsePlatform/parse-server/issues/954/events","html_url":"https://github.com/ParsePlatform/parse-server/issues/954","id":139899600,"number":954,"title":"Parse and OneSignal register for Notifications deviceToken and OneSignal's GCM registrationId incompatible","user":{"login":"432player","id":15979277,"avatar_url":"https://avatars.githubusercontent.com/u/15979277?v=3","gravatar_id":"","url":"https://api.github.com/users/432player","html_url":"https://github.com/432player","followers_url":"https://api.github.com/users/432player/followers","following_url":"https://api.github.com/users/432player/following{/other_user}","gists_url":"https://api.github.com/users/432player/gists{/gist_id}","starred_url":"https://api.github.com/users/432player/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/432player/subscriptions","organizations_url":"https://api.github.com/users/432player/orgs","repos_url":"https://api.github.com/users/432player/repos","events_url":"https://api.github.com/users/432player/events{/privacy}","received_events_url":"https://api.github.com/users/432player/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":0,"created_at":"2016-03-10T14:17:39Z","updated_at":"2016-03-10T14:17:39Z","closed_at":null,"body":"Hey guys,\r\n\r\nWe have our own Parse-Server running, using it for an Android & IPhone app.\r\nWe are also using Parse Cloud Code and the OneSignalAdapter for the Push Notifications.\r\n\r\nTo register the Android device to OneSignal we must use their SDK and register the device.\r\nThe first installation worked fine and both Tokens (in the Parse Installation Table and the Token returned from OneSignal) were compatible and the pushes arrived as expected.\r\n\r\nThe moment we uninstalled the app from the Android device and reinstalled it for some reason both Tokens from the Parse _installation table (deviceToken) and the Token returned from OneSignal were different and no more pushes reached the device.\r\n\r\nThis also happens on a couple of Android devices so we believe this issue is consistent.\r\n\r\nWe wanted to solve this issue by saving the deviceToken we receive from OneSignal and save it into the deviceToken field in the Parse _installation table. BUT, the deviceToken field in the Parse _installation table is a Readonly field (from client side).  \r\n\r\nRight now our solution is to save the deviceToken through a CloudCode function that we've written and that works for us :)\r\n\r\nFor those who have insight on this we would love some advice.\r\n\r\nCheers!\r\n"}}