diff --git a/build/updating/index.html b/build/updating/index.html
index 0303ab705dd..1cea3612e59 100644
--- a/build/updating/index.html
+++ b/build/updating/index.html
@@ -1379,6 +1379,48 @@
+
+
+
+
@@ -3625,6 +3667,48 @@
+
+
+
+
@@ -3796,9 +3880,19 @@
The Clean Derived Data option in the Utilities menu can be required for some special cases, but you probably won't need it
-Frequent Builder
-If you build frequently, you do not have to delete the profiles every time. One user reported deleting profiles gave a Revoke Certificate message - follow the link to see other reasons why that might happen. When the build script asks if you want to "Ensure a Year?", you can skip that step.
-Revoke Certificate Issue
+Frequent Builder
+If you build frequently, you do not have to delete the profiles every time. When the build script asks if you want to "Ensure a Year?", you can skip that step.
+On the other hand, you may need to delete the provisioning profiles or saved Xcode information about a version of LoopWorkspace (or other app) currently on your computer. The maintenance utilities found in the BuildSelectScrip can be run to delete your provisioning profiles or clear derived data. Or you can use the individual commands in the next sections to do the same thing.
+Delete Provisioning Profiles
+You can delete your provisioning profiles by copying this command and pasting it into any terminal. This does not affect any build you currently have on your phone - this just forces your current computer to generate a new one next time you build with Xcode
+Copy and Paste to manually remove your Provisioning Profiles on your computer rm ~/Library/MobileDevice/Provisioning\ Profiles/*.mobileprovision
+Delete Derived Data
+If you build using the same clone on your computer and then update that clone , sometimes you want to remove derived information that Xcode
+First quit out of Xcode clone on your computer, the build will take longer. All dependencies will download again. So wait until you see the "indexing" indication on Xcode
+Copy and Paste to manually force Xcode on your computer to start fresh rm -rf ~/Library/Developer/Xcode/DerivedData
+Revoke Certificate Issue
What does it look like if you run into the Revoke Certificate message? When you prepare to Sign the Targets with Xcode , you'll see the message highlighted in the figure below.
diff --git a/faqs/new-phone/index.html b/faqs/new-phone/index.html
index ab63c00ef72..0754e830df3 100644
--- a/faqs/new-phone/index.html
+++ b/faqs/new-phone/index.html
@@ -3239,7 +3239,16 @@
-
+
+
+
+
+
+ Steps Required
+
+
+
+
@@ -3318,9 +3327,9 @@
-
+
- Prepare to Change Phones
+ Prepare to Change Phone used for the Loop App
@@ -3520,7 +3529,16 @@
-
+
+
+
+
+
+ Steps Required
+
+
+
+
@@ -3599,9 +3617,9 @@
-
+
- Prepare to Change Phones
+ Prepare to Change Phone used for the Loop App
@@ -3666,7 +3684,104 @@
New Phone Tips
Overview
-Changing phones means you have to rebuild the Loop Loop Loop Loop TestFlight Mac with Xcode
+
+
Time Estimate
+
At least a few hours.
+
You can choose to keep Looping on the old phone and swap later. Most vendors give you more than a week to turn in your old device for credit.
+
+
Phone Transition Overview
+
Don't start right before a meal:
+
+Choose a time when Loop is stable and won't need much attention
+
+
Keep your old phone (if you can, connected to WiFi) and use it for the Loop
+
+Make sure Apple Health from the old phone is uploading to the iCloud
+If you are using the old phone with your Loop
+Keep the old phone connected to WiFi when convenient
+The Loop
+
+
+You want the Apple Health records created by the Loop iCloud to the new phone
+
+
+
+
Two methods to transfer your phone information (plan for 1 hour, may be faster):
+
+Do direct phone-to-phone transfer
+You will not be able to use your old or new phone during the transfer
+Both phones need to stay close to each other and on the same WiFi network
+
+
+Use iCloud backup from old phone to transfer information to the new phone
+You will not be able to use your new phone during the transfer
+
+
+
+
What happens after you transfer your phone information:
+
+Use your new phone for everything except the Loop CGM app
+You can keep using your old phone to control your pump and read your CGM until you are ready to switch to the new phone
+The new phone has the Loop records from the time the transfer started
+If you change a pod on the old phone after the transfer
+Plan to deactivate your pod on the old phone and pair the next pod on the new phone
+
+
+If you change Dexcom on the old phone after the transfer
+On the new phone, you will need to enter the new Transmitter number (G6) or wait for G7 to automatically connect
+
+
+Glucose, Insulin and Carbohydrate records created on the old phone, after the transfer, will be transferred to the new phone via Apple Health - but this may be slow
+
+
+Plan to be Open Loop when you decide to start using the Loop Loop
+
+
When ready to start using the new phone to control your app:
+
+First turn off Bluetooth on the old phone
+Review the IOB , COB and glucose trend on the old phone - that determines how long you need to run Open Loop on the new phone
+Then build Loop on the new phone
+Browser Build : Open TestFlight and Install Loop
+The TestFlight records were transferred to your new phone
+
+Mac Build: Plug the new phone into your computer
+If you recently built to your old phone, you can use the same download - otherwise, you need to Download Loop
+Your new phone will have the same name as your old phone - might want to change the display names so the two phones are different so you don't get confused in Xcode
+You will have to trust the new phone and register it
+You may need to enable Developer Mode
+If you have trouble building, you should try to reboot phone, watch, quit Xcode , restart computer, delete old provisioning profiles and then ask for help
+
+
+
+
+
+
Plan to stay in Open Loop until all Glucose, Insulin and Carbohydrate Apple Health records transfer:
+
+This can take hours
+Loop will pick up the missing records from Apple Health for insulin and glucose (but not carbohydrates)
+If you upload to Nightscout Tidepool , the carbohydrates entered with the old phone should be already uploaded so your record will be complete
+
+If you have small IOB and COB and glucose is flat, you can probably enable closed loop on the new phone without waiting for the missing records
+If there are carbs entered on old phone that are still active, plan on a longer time open loop when you transition to the new phone
+
+
+
Plan Ahead
+
+Choose when to change from old phone to new phone
+Stable glucose
+No meals planned
+
+
+Plan to use Open Loop after the transfer to allow recent Health records to transfer via iCloud
+
+
Steps Required
+Changing phones means you have to rebuild the Loop Loop Loop Loop TestFlight Mac with Xcode
+The records on the new phone are from the time you started the transfer from the old phone to the new phone. The more recent records are transferred via Apple Health. You may want to adjust carbs after the transfer because those are not read by the Loop Nightscout or Tidepool - they will show up twice. Best to have COB and IOB close to zero when you start using your new phone.
Some people don't have access to their old phone. There are instructions for handling that on this page. It makes the whole process more stressful, but remember, pods continue to deliver basal rate and Medtronic pumps can be controlled on the pump itself. Use your backup plan until you can get Loop
Forced iOS Update
When you change phones, Apple will force you to the latest iOS version available for your new phone.
@@ -3712,11 +3827,11 @@ Procure a New Phone until it is convenient to switch to the new phone
-Transfer your information to your new phone
-Let the new phone vendor help you
-Use an iCloud back-up for the transfer
+Transfer your information to your new phone. Your options are:
Use both devices with Quick Start to transfer from the old to the new phone
-
+ Use an iCloud back-up for the transfer
+Let the new phone vendor help you
+
Use the Old Phone until Ready
@@ -3757,12 +3872,26 @@ Install from TestFlight Build using Mac
+Preparatory steps:
+
+Your new phone will have the same name as your old phone - might want to change the display names so the two phones are different so you don't get confused in Xcode
+If the new phone does not have Developer Mode enabled, wait until you plug it in to try to configure it
+
+When building:
-Open Xcode
-Plug in the new phone to the computer (trust phone/computer) and hit build
+Open Xcode
+Use the same build as you used for the old phone if you built recently
+Otherwise, do a fresh download and let the BuildSelectScript open Xcode
+
+
+Plug in the new phone to the computer
+You will have to trust the computer on the new phone (and watch)
+There should be a modal pop-up in Xcode asking if you want to register the new phone
+You may need to enable Developer Mode
Build the app on the new phone
-Prepare to Change Phones
+If you have trouble finding the new phone in Xcode Xcode , restart computer, delete old provisioning profiles and then ask for help
+Prepare to Change Phone used for the Loop
On old phone (if available):
Loop RileyLink Medtronic or Eros Pods
@@ -3829,7 +3958,7 @@ Libre Check out the Transfer
-Keep closed loop disabled until you complete the full transfer and checkout.
+Stay in Open Loop (closed loop disabled) until you complete the full transfer and checkout.
Check Every Setting
@@ -3847,22 +3976,17 @@ Check out the Transfer 