Go to the shared mac either by logging into it virtually through VCU viewer (submit a helpdesk ticket for access) or by physically going to the mac.  The shared mac is usually logged in under the gen icloud account. You will need to switch to Sean's for this. Log in as Sean by going here and clicking on the username and selecting Sean Helmes.

A password box will show up. Credentials are stored on a shared spreadsheet in IT. Ask one of the IT project managers for the current password/login combo then enter it in the password box and hit enter.

The screen will redraw with Sean's desktop.

Open the xcode project for the native app you are recertifying. Go to the folder where you have saved the xcode project and click the xcode file. It will say xcodproj:

It will open in the Xcode program and look something like this:

Keep the xcode project open.

You do not need to do anything to it. But the program that generates the certificate needs it to be open or there will be a mismatch between the bundle id and the certificate id and Apple will not allow push notifications to be sent to iOS devices running the native app until it's is rectified. So it's just easier to leave it open while completing the next steps.

Open a new tab on the browser on the shared mac and go to https://onesignal.com/provisionator and click get started.

Enter Sean's apple id. His username is [email protected]. Use the same password you used to log into his account on the shared mac

Click allow on the first challenge:

Enter the verification code that pops up on screen and click the green next button:  

Click allow on the next challenge that comes up to authorize yourself to log into the provisionator using Sean's apple id.

If the platform has a green active message, then push notifications can be sent to subscribers on those platforms. Apple may force you to enter another verification code and pop up another challenge. If it does, just enter the code and click next, then click allow on the message that appears after that. Then click the green next button again to trigger more authentication madness. :)

Apple will pop up another challenge. Click allow:

Click to select the app in the drop down. Look for the same bundle id you noted down in One Signal. They need to match exactly or the certificate will NOT work:

Next, click generate. It is okay that the old certificate will be revoked because it is expired or there is an issue with it or you would not be doing this.

Apple will pop up more challenges. On the one saying that your apple id is being used to sign into a new device, click allow. On the verification pop up, click done and the certifications will generate:

Download the first certificate, the p12 file and copy the password. You do not need the other files.

Go back to onesignal.com then click Settings:

Go to the Apple iOS platform and click the gray pencil icon.

Click the check box next to "I'd like to replace my production .p12 certificate"

Choose the file you just downloaded and enter the password from the provisionator:

Click the blue next button:

Select Native iOS the click the blue next button:

Click the save button:

Refresh the page. If the status changed to active, you're all set. If there is a bundle mismatch message, refresh the provisionator and repeat steps 4 + 5.  Make sure you select the correct bundle id when you reach step 3 in the Provisionator wizard.

If the Android certification has a bundle mismatch or is expired, click here for a step-by-step guide to fix that.

If you are done, send an email to GEN editorial letting them know they can use the mac again AND change the user profile that is active back to gen by clicking on Sean's name at the top right of the screen.

Select gen and on the next screen, enter the password for the gen account so the GEN team can resume using the mac.

If you do not do this, then they will not be able to access their files.