Developer Account Status Verification for Custom App Updates

[#1]

Publishing prerequisites

Before we can begin the publishing process for the customer’s custom mobile app, the customer must first create active developer accounts on both Google and Apple platforms. For Google, account status can be verified in Google Play Console and for Apple, it can be verified in the Apple Developer platform or App Store Connect. Google also notes that inactive developer accounts may be closed if required account activity is not completed, and Apple manages account agreements through App Store Connect’s Business and Agreements sections.

Access and permissions

The customer must also ensure that SchoolMessenger/PowerSchool has been invited to the developer accounts and granted the appropriate admin-level access. On Google Play Console, user access is managed through the Users and permissions area, and Apple supports inviting additional users with the required role in App Store Connect. The detailed onboarding steps for this access setup are documented in the PowerSchool guide here: https://uc.powerschool-docs.com/communicate-customapp/latest 

Agreements

Before publishing can proceed, the customer must accept any required agreements on both platforms. Google Play Console and Apple App Store Connect both require account-level setup and agreement acceptance as part of the publishing workflow, and Apple specifically requires accepting the latest paid apps agreement in App Store Connect when applicable. These steps must be completed by the customer, since they are prerequisites for us to continue with the submission process.

Was this Article Helpful?

• Kudo this article if you found it helpful. It will help others find this resource.
• Comment directly on this article to request clarification or share feedback about the content of the article.
• Use the product-specific forum for questions not directly related to this article.

[#2]

Publishing prerequisites

Before we can begin the publishing process for the customer’s custom mobile app, the customer must first create active developer accounts on both Google and Apple platforms. For Google, account status can be verified in Google Play Console and for Apple, it can be verified in the Apple Developer platform or App Store Connect. Google also notes that inactive developer accounts may be closed if required account activity is not completed, and Apple manages account agreements through App Store Connect’s Business and Agreements sections.

Access and permissions

The customer must also ensure that SchoolMessenger/PowerSchool has been invited to the developer accounts and granted the appropriate admin-level access. On Google Play Console, user access is managed through the Users and permissions area, and Apple supports inviting additional users with the required role in App Store Connect. The detailed onboarding steps for this access setup are documented in the PowerSchool guide here: https://uc.powerschool-docs.com/communicate-customapp/latest 

Agreements

Before publishing can proceed, the customer must accept any required agreements on both platforms. Google Play Console and Apple App Store Connect both require account-level setup and agreement acceptance as part of the publishing workflow, and Apple specifically requires accepting the latest paid apps agreement in App Store Connect when applicable. These steps must be completed by the customer, since they are prerequisites for us to continue with the submission process.

Was this Article Helpful?

• Kudo this article if you found it helpful. It will help others find this resource.
• Comment directly on this article to request clarification or share feedback about the content of the article.
• Use the product-specific forum for questions not directly related to this article.

[#3]

Publishing prerequisites

Before we can begin the publishing process for the customer’s custom mobile app, the customer must first create active developer accounts on both Google and Apple platforms. For Google, account status can be verified in Google Play Console and for Apple, it can be verified in the Apple Developer platform or App Store Connect. Google also notes that inactive developer accounts may be closed if required account activity is not completed, and Apple manages account agreements through App Store Connect’s Business and Agreements sections.

Access and permissions

The customer must also ensure that SchoolMessenger/PowerSchool has been invited to the developer accounts and granted the appropriate admin-level access. On Google Play Console, user access is managed through the Users and permissions area, and Apple supports inviting additional users with the required role in App Store Connect. The detailed onboarding steps for this access setup are documented in the PowerSchool guide here: https://uc.powerschool-docs.com/communicate-customapp/latest 

Agreements

Before publishing can proceed, the customer must accept any required agreements on both platforms. Google Play Console and Apple App Store Connect both require account-level setup and agreement acceptance as part of the publishing workflow, and Apple specifically requires accepting the latest paid apps agreement in App Store Connect when applicable. These steps must be completed by the customer, since they are prerequisites for us to continue with the submission process.

Was this Article Helpful?

• Kudo this article if you found it helpful. It will help others find this resource.
• Comment directly on this article to request clarification or share feedback about the content of the article.
• Use the product-specific forum for questions not directly related to this article.