{"_id":"590a04f8ed80861900cbc7b9","user":"55b2d5626862a10d00887af9","__v":0,"project":"55b2d5baa74a380d00e290c4","version":{"_id":"590a04f2ed80861900cbc737","project":"55b2d5baa74a380d00e290c4","__v":4,"createdAt":"2017-05-03T16:27:30.085Z","releaseDate":"2017-05-03T16:27:30.085Z","categories":["590a04f3ed80861900cbc738","590a04f3ed80861900cbc739","590a04f3ed80861900cbc73a","590a04f3ed80861900cbc73b","590a04f3ed80861900cbc73c","590a04f3ed80861900cbc73d","590a04f3ed80861900cbc73e","590a04f3ed80861900cbc73f","590a04f3ed80861900cbc740","590a04f3ed80861900cbc741","590a04f3ed80861900cbc742","590a04f3ed80861900cbc743","590a04f3ed80861900cbc744","590a04f3ed80861900cbc745","590a04f3ed80861900cbc746","590a04f3ed80861900cbc747","590a04f3ed80861900cbc748","590a04f3ed80861900cbc749","590a04f3ed80861900cbc74a","590a04f3ed80861900cbc74b","590a04f3ed80861900cbc74c","590a04f3ed80861900cbc74d","59124949de13f61900336a7a","5914b04e7c2c552d008b7104","5914b47242c6a22300b9dc20"],"is_deprecated":false,"is_hidden":false,"is_beta":false,"is_stable":true,"codename":"","version_clean":"7.0.0","version":"7"},"parentDoc":null,"category":{"_id":"590a04f3ed80861900cbc74c","__v":0,"version":"590a04f2ed80861900cbc737","project":"55b2d5baa74a380d00e290c4","sync":{"url":"","isSync":false},"reference":false,"createdAt":"2016-01-05T19:32:59.974Z","from_sync":false,"order":22,"slug":"troubleshooting","title":"Troubleshooting"},"updates":[],"next":{"pages":[],"description":""},"createdAt":"2017-03-07T15:39:33.344Z","link_external":false,"link_url":"","githubsync":"","sync_unique":"","hidden":false,"api":{"results":{"codes":[]},"settings":"","auth":"required","params":[],"url":""},"isReference":false,"order":16,"body":"Our SDK allows your testers to be notified when a new version of your application is available [via an alert](doc:automatic-update). Here a checklist of the conditions required for this feature to work.\n[block:api-header]\n{\n  \"title\": \"Enable the automatic app-update\"\n}\n[/block]\nThe Automatic App-Update is activated by default but check your App Settings to make sure it is still enabled. If it's not, then your users won't get notified that a new version is available next time they open your app.\n[block:image]\n{\n  \"images\": [\n    {\n      \"image\": [\n        \"https://files.readme.io/0bfbc2e-SDK_-_Feature_settings_-_Automatic_App-Update.png\",\n        \"SDK - Feature settings - Automatic App-Update.png\",\n        3000,\n        800,\n        \"#ecf1f1\"\n      ]\n    }\n  ]\n}\n[/block]\n\n[block:api-header]\n{\n  \"title\": \"The build must be deployed via email\"\n}\n[/block]\nUsers will only be notified about new **deployed** versions of your application. Make sure that you either **manually deployed** a new build:\n[block:image]\n{\n  \"images\": [\n    {\n      \"image\": [\n        \"https://files.readme.io/692de5e-Deployments_-_manual.png\",\n        \"Deployments - manual.png\",\n        1500,\n        869,\n        \"#2e93cd\"\n      ]\n    }\n  ]\n}\n[/block]\nOr that you use [automated deployment](doc:deploy-automatically).\n[block:image]\n{\n  \"images\": [\n    {\n      \"image\": [\n        \"https://files.readme.io/f6bc918-Deployments_-_automatic_-_1.png\",\n        \"Deployments - automatic - 1.png\",\n        1500,\n        528,\n        \"#edf1f2\"\n      ],\n      \"caption\": \"Automatically deploying a new version of the app after a successful build\"\n    }\n  ]\n}\n[/block]\n\n[block:api-header]\n{\n  \"title\": \"The SDK must be installed on the previous version of the app\"\n}\n[/block]\nIf your users are running a version they installed **before** you integrated the SDK into your application, they won't get notified about the new version available via the app. \n\nThey will have to install the new build via the notification they got via email. Once this build is installed, they will be notified of the subsequent available versions of your application.\n[block:api-header]\n{\n  \"title\": \"The user must be identified\"\n}\n[/block]\nWe need to be able to identify the user before showing the new version alert. To achieve that, we use a certificate. To ensure that the user not getting the notification is properly identified, use the feedback feature of the SDK.\n\n1. Take a screenshot\n2. Submit feedback\n\nIf the feedback appears from an **Unknown user** then something went wrong with the user's device. To fix it, ask your user to perform the following tasks in the **General** > **Profile** section of the **Settings panel**.\n[block:image]\n{\n  \"images\": [\n    {\n      \"image\": [\n        \"https://files.readme.io/f78af09-Remove_certificate.png\",\n        \"Remove certificate.png\",\n        1500,\n        915,\n        \"#ececf3\"\n      ],\n      \"caption\": \"Remove the buddybuild certificate\"\n    }\n  ]\n}\n[/block]\nThen, visit https://dashboard.buddybuild.com/reset **in Safari on your iPhone**. Once this is done, you can ask your users to visit the installation page again.\n[block:api-header]\n{\n  \"title\": \"User must only have one device registered\"\n}\n[/block]\nCurrently, the update notification is keyed to the user's **email address**, not the device. Installing a new version on the iPad will **cancel the update notification** from showing on the iPhone.","excerpt":"","slug":"user-not-getting-alert-when-a-new-version-of-app-is-available","type":"basic","title":"User not getting alert when a new version of app is available"}

User not getting alert when a new version of app is available


Our SDK allows your testers to be notified when a new version of your application is available [via an alert](doc:automatic-update). Here a checklist of the conditions required for this feature to work. [block:api-header] { "title": "Enable the automatic app-update" } [/block] The Automatic App-Update is activated by default but check your App Settings to make sure it is still enabled. If it's not, then your users won't get notified that a new version is available next time they open your app. [block:image] { "images": [ { "image": [ "https://files.readme.io/0bfbc2e-SDK_-_Feature_settings_-_Automatic_App-Update.png", "SDK - Feature settings - Automatic App-Update.png", 3000, 800, "#ecf1f1" ] } ] } [/block] [block:api-header] { "title": "The build must be deployed via email" } [/block] Users will only be notified about new **deployed** versions of your application. Make sure that you either **manually deployed** a new build: [block:image] { "images": [ { "image": [ "https://files.readme.io/692de5e-Deployments_-_manual.png", "Deployments - manual.png", 1500, 869, "#2e93cd" ] } ] } [/block] Or that you use [automated deployment](doc:deploy-automatically). [block:image] { "images": [ { "image": [ "https://files.readme.io/f6bc918-Deployments_-_automatic_-_1.png", "Deployments - automatic - 1.png", 1500, 528, "#edf1f2" ], "caption": "Automatically deploying a new version of the app after a successful build" } ] } [/block] [block:api-header] { "title": "The SDK must be installed on the previous version of the app" } [/block] If your users are running a version they installed **before** you integrated the SDK into your application, they won't get notified about the new version available via the app. They will have to install the new build via the notification they got via email. Once this build is installed, they will be notified of the subsequent available versions of your application. [block:api-header] { "title": "The user must be identified" } [/block] We need to be able to identify the user before showing the new version alert. To achieve that, we use a certificate. To ensure that the user not getting the notification is properly identified, use the feedback feature of the SDK. 1. Take a screenshot 2. Submit feedback If the feedback appears from an **Unknown user** then something went wrong with the user's device. To fix it, ask your user to perform the following tasks in the **General** > **Profile** section of the **Settings panel**. [block:image] { "images": [ { "image": [ "https://files.readme.io/f78af09-Remove_certificate.png", "Remove certificate.png", 1500, 915, "#ececf3" ], "caption": "Remove the buddybuild certificate" } ] } [/block] Then, visit https://dashboard.buddybuild.com/reset **in Safari on your iPhone**. Once this is done, you can ask your users to visit the installation page again. [block:api-header] { "title": "User must only have one device registered" } [/block] Currently, the update notification is keyed to the user's **email address**, not the device. Installing a new version on the iPad will **cancel the update notification** from showing on the iPhone.