Hello Intel XDK and forum Users,
As of today (June 26, 2015) we have finished our migration of Intel XDK accounts to the more secure intel.com login system (the same login system you use to access this forum). You will see a new login screen when providing your userid and password to the Intel XDK, and to App Preview. This is the intel.com login system you are seeing. Other than the change to a new login screen, there will be no difference for the majority of Intel XDK users.
We have migrated nearly all active users to the new login system, as communicated earlier on this forum (see that post below). Unfortunately, there are a few active user accounts that we could not automatically migrate to intel.com, primarily because the intel.com login system does not allow the use of some characters in userids that were allowed in the old login system.
If you have not used the Intel XDK during the past 3-4 months, your account may not have been automatically migrated. If you own one an "inactive" account it will have to be manually migrated -- please try logging into the Intel XDK with your old userid and password, to determine if it no longer works. If you find that you cannot login to your existing Intel XDK account, and still need access to your old account, please send a private message using this thread (use the "Send Author a Message" link at the top of this post) and include your userid and the email address associated with that userid in that private message, so we can guide you through the steps required to reactivate your old account.
Alternatively, you can create a new Intel XDK account (or simply use the userid and password you now use for this forum). If you have submitted an app to the Android store from your old account you will need access to that old account to retrieve the Android signing certificates in order to upgrade that app on the Android store; in that case, creating a new account is not advised.
Thanks,
-- the Intel XDK team
------ Problems with Multiple Accounts and Android Certificate Signing Alerts ----
Each Intel XDK account has a unique Android developer certificate. That unique certificate must be used each time you update apps to the Android store that were originally built with that account. This means apps built and published with account “A” must be updated with the Android certificate stored in account “A” and those built and published using account “B” must be updated with the Android certificate stored in account “B.”
If you have only published apps to the Android store with one Intel XDK account, the certificate in that account is the only important one. If you have successfully published apps built with both accounts you must continue to use both certificates for future updates to those apps. Note that apps that have never been published to the store are not important to this discussion, with regard to certificates.
If you do have two (or more) published apps, built using both accounts, you have the following options:
-- continue to use the existing accounts to build updates for each of those apps
-- retrieve the certificates from your Intel XDK accounts and self-sign those apps (help required from Intel)
If you have only published apps built with one account, you have the following options:
-- delete the non-published account and only use the account that was used to build your published apps
-- merge the two accounts (help required from Intel) so only one account uses the “correct” certificate
-- retrieve your published certificate from your Intel XDK account and self-sign all apps (help required from Intel)
Before doing the above, if you created the second account because you couldn’t get logged into your first account, then please go to https://signin.intel.com using the username from your first account and click the “Forgot Your Password?” link to reset your password. After you have reset your password you can access the Intel XDK with the original username and any builds you perform will be signed using your original certificates.
We can merge your two accounts, which would leave you with one of the two existing certificates. This would prevent you from updating an application with the account you choose to remove. We can remove the certificates associated with Account "A" and instead use the certificates from Account "B," or vice-versa. If you choose such an option, your existing certificates for one of the accounts will be no longer recoverable.
Finally, we can send both of your existing Android account certificates to you and you can choose to use the XDK to build un-signed applications, which you would then re-sign yourself (locally on your development machine) using the certificate of choice.
NOTE: once a certificate is lost it cannot be retrieved.
-- the Intel XDK team
-------- Incorrect Login Redirect with App Preview --------
In a few rare instances you may see an "appcenter" page like that shown in the image below when logging into App Preview from your device. Click the big X in the upper right corner of the page and the App Preview login should continue properly. This is a known issue that is awaiting a resolution.
-------- Original Login Changes Post --------
Hello Intel XDK and forum Users,
In an effort to unify Intel XDK users accounts completely with Intel Developer Zone (and intel.com), part of our final phase of migration is starting today. So far, we have (mostly) silently enabled new and existing XDK user accounts access intel.com and Intel Developer Zone. Starting today, we will be providing the existing Intel Developer Zone (IDZ) users access to Intel XDK. In doing so, you may get confused as to whether to use your old XDK login or the IDZ one. To avoid login confusion, here are the possible scenarios, it will help you understand your particular case. You fall into one of these 4 categories -- the first three require nothing extra for you to do.
- You have an existing XDK account (but do not have IDZ account): We have created an IDZ account with the same username as your XDK account and you can log into XDK and IDZ both using this account.
- You are a new user and you registered for Intel XDK: Along with your XDK account creation you get access to IDZ using the same credentials.
- You have an existing IDZ account (but no XDK account): You will be able to login into XDK using your IDZ credentials after you accept the terms and conditions on XDK login page.
- You have existing XDK account and existing IDZ account:
- If you had same login username and password for XDK and IDZ account you will continue to use the same for both.
- If your usernames for XDK and IDZ accounts are same but passwords are different – you will be prompted to merge your accounts and enter your intel.com password. After you enter “validate and Merge”, you will be able to use this credentials to log in into both XDK and IDZ.
- If Your XDK username and IDZ usernames were different:
- Now you have two intel.com accounts, You will be able to login into IDZ using both credentials.
- You will be able to login into XDK using your existing XDK username as usual and also using your IDZ account credentials after you agree to terms and conditions on XDK login page.
- When you login into XDK using your IDZ account credentials, it’s going to be a new XDK account so you will not be able to access your existing project or certificates during that login session, so it is recommended that you continue using your current XDK account credentials so you have access to your existing projects and certificates.
-- the Intel XDK team
Link Copied
App Preview 2.4 is only available for the Android version -- the iOS version is still 2.3.3. The changes in the Android version were needed to support the new Debug tab features that are part of the Early Access release, otherwise, there is no difference when compared to the iOS version.
When using the local tab in App Preview your device must be on the same local subnet as your workstation AND the Intel XDK Test tab must be set to "WIFI" (see the image below). You may also have to push the "Update Server" button to get your device to see the XDK. If they are on different subnets this function will not work.
That said, I tried to confirm that things are working correctly and they are not working correctly with either iOS or Android. I will inform engineering.
