Errors

Introduction

If you are reading this document it is probably because you encountered an error in the GROW platform. Do not worry, below you will find an inventory of basic errors as well as its related troubleshooting!

Each section refers to a specific menu in the GROW product, a sub-section can refer to a specific action where those errors can be encountered as the errors will not be the same depending on the action you are performing!

The login form is accessible through https://app.bryj.ai. Your can find below the errors which could be encountered upon click on Login.

Message	Cause	Possible solutions
Please include an “@” in your email address. <input> is missing an “@”	Invalid email format	This email is not valid. Check your email input
Please enter a part following <invalid-email-with-@>. <invalid-email-with-@> is incomplete	The email has been detected as incomplete. This can happen if you put name@ instead of name@mycompany.com for example	Check the Email Address field. Your input is missing some characters.
Invalid Email or password	The couple email password is invalid	Verify there are no typos in your email and password. If you fail to remember your password start the password recovery process by clicking on the Forgot password? button.
reCAPTCHA verification failed, please try again	Wrong answers provided during the CAPTCHA verification.	Perform the CAPTCHA verification again
Your workspace is disabled, please contact your CSM. You tried to access a disabled workspace Contact your CSM	You tried to access a disabled workspace	Contact your CSM

Password recovery email request

This screen is accessible when starting the password recovery procedure from the login screen. Upon click on Send Reset Link the following errors can be encountered.

Message	Cause	Possible solutions
Please include an “@” in your email address. <input> is missing an “@”	Invalid email format	This email is not valid. Check your email input
Please enter a part following <invalid-email-with-@>. <invalid-email-with-@> is incomplete	The email has been detected as incomplete. This can happen if you put name@ instead of name@mycompany.com for example	Check the Email Address field. Your input is missing some characters.

Password recovery change password

This page is accessible by clicking on the link sent in the password recovery email. The following errors can be encountered upon click on Reset Password.

Message	Cause	Possible solutions
Password confirmation doesn’t match Password	The inputs in the password and password confirmation fields are not the same	Verify your password and password confirmation are the same
Password must contain at least one digit	A digit is missing in your password	Add a digit in your password (and password confirmation)
Password must contain at least one punctuation mark or symbol	A punctuation mark or symbol is missing in your password	Add punctuation mark or symbol in your password (and password confirmation)
Password must contain at least one upper-case letter	An upper-case letter is missing in your password	Add as upper-case letter in your password (and password confirmation)

Your profile is unable to access content

Your login may be successful but depending on your account status and permissions you may land on a welcome screen displaying an error.

Message	Cause	Possible solutions
You do not have any allocated project.  Please contact your admin	Your admin removed your permissions on all projects in the workspace, so you do not have access to anything.	Contact your admin to restore your permissions
Your account has been disabled by your Workspace admin.  Please contact your admin	Your admin de-activated your account.	Contact your admin
You do not have sufficient permissions to access this page	You try to access an URL not available for your profile (for example, project administration if you are a project viewer)	Contact your admin to modify your permissions if you need access to this URL. Go to https://app.bryj.ai to access pages you are allowed to view.

General

General errors can be encountered at any time on the platform.

Message	Cause	Possible solutions
404	Page not available	Go to https://app.bryj.ai to access pages you are allowed to view.If you are unable to view the content (outside of a scheduled maintenance window), contact your CSM.
Unexpected server error	Resource not available on the server, technical calls wrongly formatted… There are multiple origins to this error	If the error persists, contact your support and send then your steps to reproduce the error.

Dashboard

Some errors can be encountered while trying to display data on the dashboard https://app.bryj.ai/dashboard/

Message	Cause	Possible solutions
There is no content available as no apps are configured yet.Please add an app to <project-name> project administration.	For the selected project, no apps had been configured to enable GROW engagement capabilities	Switch the project in the project picker if you are not observing the correct one already. If the selected project is correct, proceed with the setup of your apps in Project Administration.
No data to display over selected period	GROW did not collecct any data over the selected period.	Select another period in the date picker. Contact your CSM if this behavior seems abnormal to you.

Audiences

Audiences are key to enable GROW engagement capabilities.

Custom audience creation errors

Errors could be encountered during the Audience creation process upon click on “Create audience” at the bottom right

Message	Cause	Possible solutions
Please give a name to the audience	The custom audience is missing a name.	Set a name for your custom audience in the first block of the editor. The field will be highlighted in red.
Please add a filter to your audience	No filters are set for your new custom audiences. As creating a custom audiences with no filters is useless, we do not allow you to do that.	Configure at least one filter in your audience
Cannot be created: Information missing	One or several filters added are not configured / have information missing. This error can also be shown if your audience name is missing	Check the fields highlighted in red in the audience editor. Fill in those fields.If your audience is set for all live apps. Make sure filters with specific conditions on iOS and Android (events, app version…) are filled for both OS.

Audience activation / de-activation errors

Message	Cause	Possible solutions
Maximum number of active audiences reached	For hard limit only, if your active audience quota is reached this error will be fired if you try to activate another audience!	De-activate an active audience to free a spot. Contact your CSM to upgrade your plan

Campaign

Campaigns are used to engage with your mobile apps end-users. It’s important you know how to debug issues related to your campaign creation or performance monitoring.

Campaign creation

Message	Cause	Possible solutions
Please give a name to your campaign.	You attempted to skip the first step of campaign creation and go to campaign type directly.	Add a campaign name
Please select a start date for your campaign.	You attempted to leave this date empty.	Set your campaign start date by picking a date and time or select the “now” option
Start date shouldn’t be in the past.	In the delivery time step, you attempted to select a date in the past OR you resumed a draft with a campaign start date set in the past.	Edit the start date and select a date and time in the future.
You need to give a title to your push.	Missing a push title	Provide a title
You need to give a message to your push.	Missing a push message	Provide a message
Variable already exists.	You tried to add a variable with the name that has already been taken	Choose any name that has not been taken
Cannot send push campaign. Push settings are missing in project configuration.	A campaign type push has been selected but in the Audience step, targeted app is missing push settings configuration. This configuration is required to enable push sending.	Go to project settings and set your .p8 for iOS and your FCM / HCM for android.

Test message – campaign preview

In the compose step the Test message feature is accessible thanks to the Test Message CTA at the top right of the block.

Message	Cause	Possible solutions
App was uninstalled from device	The targeted device has uninstalled the application	Reinstall application on target device or provide a device with the application installed
Bad push token	Push token provided is invalid	On an iOS app this error can be related to an incorrect .p8 configured in push settings. If you are testing an iOS live app, edit the live app push settings, if your are testing a QA app, edit the QA push settings. If you previously had pushes working on this device before and it suddenly stopped. It probably means your token was refreshed by your device… in this case you would not have any other option than waiting for the new token to be ingested.
Sending status unavailable. Please check check push reception directly on your device.	When sending a push, information on the push sending status was not collected due to a technical error.	Verify push reception on your device. Try to send the push again (this is often a temporary error). Contact support if the issue persists.
Unknown device	The targeted device id is unknown to GROW.	Perform a device registration to make sure the device id you try to send the notification on is related to your device. If you just installed the app, wait few hours for your information to be processed.
Opt out	Device is not opt in according to latest GROW information. Please note your device associated information will be based on your workspace data freshness (frequency on which we update and process data).	Your device may: be opt-out for push notifications locally. In that scenario, opt-in for push notifications and wait for your new device information to be processed before sending a push again.be opt-in for push notifications locally BUT the opt-in occurred recently so this new information is not yet available in GROW (based on your data freshness)
No token registered for this device yet	Your device is new and its token has not been registered yet.	Try to send the push again in a couple of hours.
No push settings defined	Can happen for Android devices if the project push settings are not properly configured.	Add FCM Key in your project push settings. If you are testing an Android live app, edit the live app push settings, if your are testing a QA app, edit the QA push settings.
This type of file is not supported. Please try again.	While configuring a rich push, you tried to upload a file format which is not supported	Review the supported extensions and upload a file which match those constraints.
Upload failed. Please upload another file and try again	While configuring a rich push, you tried to upload a file which includes a modified extension.	Check if your file is opening properly in your computer. If not, upload another file.
Uploaded file is too heavy	While configuring a rich push, the uploaded media is larger than the maximum allowed size	Upload a smaller file.
Invalid deep link	While configuring a deep link in a push or an in-app, it must contain a ://. If there is an input but no ://, the error will be displayed	Verify your deep link format. Some valid format examples could be <appbundle>://<deeplink> ; anything supported by your app

Debug

Live requests

Message	Cause	Possible solutions
Timeout	The live request page times out (technical error)	Refresh the page itself or click on the refresh CTA available.

Send message

Message	Cause	Possible solutions
App was uninstalled from device	The targeted device has uninstalled the application	Reinstall application on target device or provide a device with the application installed
Bad push token	Push token provided is invalid	On an iOS app this error can be related to an incorrect .p8 configured in push settings. If you are testing an iOS live app, edit the live app push settings, if your are testing a QA app, edit the QA push settings. If you previously had pushes working on this device before and it suddenly stopped. It probably means your token was refreshed by your device… in this case you would not have any other option than waiting for the new token to be ingested.
Sending status unavailable. Please check check push reception directly on your device.	When sending a push, information on the push sending status was not collected due to a technical error.	Verify push reception on your device. Try to send the push again (this is often a temporary error). Contact support if the issue persists.
Unknown device	The targeted device id is unknown to GROW.	Perform a device registration to make sure the device id you try to send the notification on is related to your device. If you just installed the app, wait few hours for your information to be processed.
Opt out	Device is not opt in according to latest GROW information. Please note your device associated information will be based on your workspace data freshness (frequency on which we update and process data).	Your device may: be opt-out for push notifications locally. In that scenario, opt-in for push notifications and wait for your new device information to be processed before sending a push again.be opt-in for push notifications locally BUT the opt-in occurred recently so this new information is not yet available in GROW (based on your data freshness)
No token registered for this device yet	Your device is new and its token has not been registered yet.	Try to send the push again in a couple of hours.
No push settings defined	Can happen for Android devices if the project push settings are not properly configured.	Add FCM Key in your project push settings. If you are testing an Android live app, edit the live app push settings, if your are testing a QA app, edit the QA push settings.
File is missing	You selected the rich push option but you did not provide a media for the rich content	Upload a rich media matching the requirements listed in the UI (format and size of the file).
This type of file is not supported. Please try again.	While configuring a rich push, you tried to upload a file format which is not supported	Review the supported extensions and upload a file which match those constraints.
Upload failed. Please upload another file and try again	While configuring a rich push, you tried to upload a file which includes a modified extension	Check if your file is opening properly in your computer. If not, try to upload another file.
Uploaded file is too heavy	While configuring a rich push, the uploaded media is larger than the maximum allowed size	Upload a smaller file.
Invalid deep link	While configuring a deep link in a push or an in-app, it must contain a ://. If there is an input but no ://, the error will be displayed	Verify your deep link format. Some valid format examples could be <appbundle>://<deeplink> ; anything supported by your app
Device has not sent test data yet	This error is really rare, it is due to sync delay to ingest your device information in the test devices list. This error prevents the use of Send message	There is a workaround by using the Campaign test device capabilities to check push / in-app rendering.If the error persists for more than 4 hours, contact support.

Admin

Project management

Message	Cause	Possible solutions
Maximum number of projects reached	When creating a project if you have a plan with a hard limit and you reached your maximum allowed number of projects, this error will be displayed.	Delete one of your projects to free up a spotContact your CSM to upgrade your plan
Name can’t be blank	When adding a new project / app or editing an existing project / app, its name cannot be empty.It’s the same for attributes creation and edition as well.	Do not set a blank project name or attribute name.
Bundle ID can’t be blank	When adding a new app in a project, its bundle id cannot be empty.	Do not set a blank bundle id
Missing information	When adding an app, an attribute, anything really… if you fail to fill in some information in the form you may encounter this error	Fill in the information in the highlighted fields in the form
Bundle ID is invalid	When adding an app if you provided an invalid package name / bundle id this error will be displayed	Verify your bundle id input in the app creation form. It should contain at least one “.” inside the bundle (not at the beginning or the end), no other special characters, no spaces.
Bundle ID has already been taken	When adding an app if you provided a package name / bundle id which is already taken by the same app type (iOS / Android) in your project, in another project or even another workspace this error will be fired.	Check you selected the correct app type (iOS / Android)Check the bundles of the other apps available in the projectCheck the bundles of the other projects in the workspaceIf none of the above allowed you to determine where is the duplicate and fix it yourself. Contact support to start an investigation
This project already has an iOS Live app, please review your app configuration	The project has only one live app – iOS app, and you tried to add the second iOS Live app	A project can have only one iOS live app. Add the other project if you need an additional iOS Live app
This project already has an Android Live app, please review your app configuration	The project has only one live app – Android app, and you tried to add the second Android Live app	A project can have only one Android live app. Add the other project if you need an additional Android live app
This project already has Live apps set, please review your app configuration	The project has two live apps – iOS and Android. You tried to add the other live app	A project can have only two live apps – one iOS and one Android. Add the other project if you need an additional live app
The maximum number of API Keys is 5.	When adding API keys, if you try to add more than 5 API keys, this error will be fired.	You need to de-activate and delete one of the API keys listed to be able to add a new one.
Please provide an FCM key.	When configuring Android push settings, if you do provide an FCM key or leave the field empty you will encounter this error	Add the FCM key retrieved from the Firebase console for the apps your have configured in your GROW projectDisabled Android Google push setting.
Please provide a Huawei app ID.	When configuring Android push settings, if you do provide an Huawei app ID or leave the field empty you will encounter this error	Add the Huawei app ID retrieved from your Huawei console for the apps configured in your GROW projectDisable Android Huawei push settings.
Please provide a Huawei app secret.	When configuring Android push settings, if you do provide an Huawei app secret or leave the field empty you will encounter this error	Add the Huawei app secret retrieved from your Huawei console for the apps configured in your GROW projectDisable Android Huawei push settings.
This type of file is not supported. Please try again.	When configuring iOS push settings, if you do not upload a .p8 you will encounter this error	Upload the .p8 retrieved from the apple store for the apps your have configured in your GROW project

User management

User management refers to all the errors encountered in the Users tab of the administration menu.

Message	Cause	Possible solutions
Maximum number of active licences reached	If you have a hard limit subscription. If you try to add / activate a user while you already reached the maximum number of active licences in your plan, this error will be shown	De-activate an active licence or delete a user to free an active licence. Contact your CSM to upgrade your plan.
Missing information	When starting to add a user, this error will be shown if you did not fill:type of account to create (workspace admin or project role)First name of the userLast name of the user	Fill the missing fields highlighted in red.
Invalid email format	If you email format is incorrect (no @, spaces in the emails…) this error will be triggered.	Check the email of the user you intend to invite and fix typo issues.
First name can’t be blank	If you tried to submit the form with the first name field containing only spaces, this error will be shown.	Enter a valid First name (at least one character).
Last name can’t be blank	If you tried to submit the form with the last name field containing only spaces, this error will be shown.	Enter a valid Last name (at least one character).
Add at least 1 role for the user	If you tried to invite a project role user without configuring at least one project role, this error will be shown. If no roles are configured this user will not have access to anything… This is why this action is not allowed.	Configure at least one project role before resubmitting the form.