PressPlay displays various error messages when things go wrong. This comprehensive reference explains what these errors mean, what causes them, and how to resolve them. Use this as a quick reference guide when encountering unfamiliar errors.
PressPlay errors typically include:
Error code: Numeric or alphanumeric identifier (e.g., "E1001", "HTTP 400")
Error message: Human-readable description of what went wrong
Context: Where the error occurred (experiment creation, sync, etc.)
Timestamp: When the error happened
Suggested action: Immediate steps to resolve (when available)
Error messages appear in several places: toast notifications, inline on forms, in activity logs, or on dedicated error pages.
What it means: Your login credentials or session token isn't valid.
Common causes:
Session expired after period of inactivity
Logged out in another tab or device
Account password was changed
Authentication token was manually revoked
How to fix:
Sign out completely
Clear browser cache and cookies
Sign back in with current credentials
If problem persists, try password reset
What it means: You're authenticated but don't have permission for this action.
Common causes:
Account role doesn't allow this action (e.g., Viewer trying to create experiment)
Trying to access another team's resources
Google Play Console permissions insufficient
App or experiment belongs to different publisher
How to fix:
Check your role in team settings (need Editor or Admin)
Verify you have correct permissions in Google Play Console
Ensure you're in the correct team account
Contact team admin to elevate permissions if needed
What it means: OAuth connection to your Google Play Console account is no longer valid.
Common causes:
Google OAuth token expired
You revoked PressPlay access in Google settings
Google password was changed
Security event triggered token revocation
How to fix:
Go to Settings → Publishers
Find disconnected publisher
Click "Reconnect" or "Connect Publisher"
Complete OAuth flow again
Grant all requested permissions
What it means: PressPlay couldn't synchronize data with Google Play Console.
Common causes:
Temporary API connectivity issue
Rate limiting from too many sync requests
App no longer accessible or was removed
Permission changes in Play Console
How to fix:
Wait 5 minutes and try manual sync again
Verify app still exists in Play Console
Check publisher connection status
Reconnect publisher if connection is lost
Check PressPlay status page for known issues
What it means: You've made too many API requests in a short time.
Common causes:
Clicking "Sync Now" repeatedly
Creating many experiments simultaneously
Multiple team members triggering syncs
Automated tools hitting API limits
How to fix:
Wait 10-15 minutes before retrying
Avoid repeatedly clicking sync buttons
Let automatic background sync handle updates
Space out bulk operations
What it means: Google Play Console API or PressPlay service is temporarily down.
Common causes:
Google API maintenance or outage
PressPlay infrastructure issue
High load causing temporary degradation
How to fix:
Wait 15-30 minutes and retry
Check PressPlay status page
Verify Google Play Console is accessible directly
Don't repeatedly retry (can worsen load)
What it means: Your experiment setup doesn't meet requirements.
Common causes:
Traffic allocation doesn't total 100%
Variant missing required assets
Start date is in the past
End date before start date
No variants defined
Duplicate variant names
How to fix:
Review all experiment settings for validation errors
Check that traffic percentages sum to exactly 100%
Ensure all required fields are filled
Verify date ranges are logical
Complete all variants before creating experiment
What it means: Another experiment is already testing the same elements.
Common causes:
Active experiment testing same asset type (e.g., two icon tests)
Manual experiment in Play Console not created through PressPlay
Recently stopped experiment still cleaning up
How to fix:
Check for other active experiments on this app
Review Google Play Console for manual tests
Wait 5-10 minutes if you just stopped a conflicting test
Modify new experiment to test different elements
Pause or complete conflicting experiment first
What it means: Experiment can't be launched in current state.
Common causes:
Assets still generating
Validation failures on one or more variants
App not published in target markets
Publisher connection lost
Insufficient permissions
How to fix:
Check experiment status - should show "Ready"
Verify all variants show green checkmarks
Review any validation errors
Ensure app is published in target countries
Check publisher connection is active
What it means: AI couldn't generate the requested asset.
Common causes:
Content policy violation
AI service timeout
Insufficient app information
Invalid generation parameters
Technical error in rendering pipeline
How to fix:
Review error details for specific cause
Adjust generation prompts to avoid policy issues
Try simpler generation parameters
Ensure app has complete store listing
Wait a moment and try again
Upload manually created asset if AI continues failing
What it means: Generated content violates Google Play or content safety policies.
Common causes:
Generated text contains prohibited terms
Health, financial, or sensitive topic claims
Misleading or unsubstantiated statements
Competitor references
How to fix:
Review Google Play content policies
Modify generation prompts to avoid sensitive topics
Use different value propositions or messaging angles
Create assets manually if AI consistently fails
What it means: Generated asset doesn't meet Google Play technical requirements.
Common causes:
Incorrect image dimensions
File size too large (over 8MB)
Wrong aspect ratio
Text exceeds character limits
Missing transparency (for icons)
Invalid file format
How to fix:
Check Google's requirements for specific asset type
Regenerate with correct dimensions specified
Compress large images
Trim text to fit character limits
Ensure proper file format (PNG for images, etc.)
What it means: You've reached your plan's asset generation limit.
Common causes:
Hit daily or monthly generation quota
Too many rapid generation requests
Free tier limitations
How to fix:
Wait for quota reset (typically daily or monthly)
Review your plan limits in account settings
Upgrade to higher tier for more generations
Use existing assets or manually created ones
Prioritize which assets really need AI generation
What it means: No statistics available for requested timeframe or experiment.
Common causes:
Experiment too new (data has 24-48 hour delay)
App has insufficient traffic
Experiment not actually running
Date range has no impressions
Data sync hasn't occurred yet
How to fix:
Wait 48 hours after starting experiment
Verify experiment shows "Running" status
Check experiment exists in Google Play Console
Adjust date range to include data
Force data sync if available
What it means: Not enough data to calculate statistical significance.
Common causes:
Experiment too new or short-running
Low traffic app
Too many variants splitting traffic thin
Narrow target market with low volume
What to do:
Continue running experiment to collect more data
Consider reducing number of variants
Expand target markets if appropriate
Accept that some apps need longer test durations
What it means: Form submission missing required information.
Common causes:
Skipped required form field
Field appears filled but contains only whitespace
Browser autofill didn't complete properly
How to fix:
Look for fields marked with red indicators
Scroll through entire form to find empty required fields
Ensure no fields contain only spaces
Complete all fields before submitting
What it means: Data entered doesn't match expected format.
Common examples:
Email address missing @ symbol
Date in wrong format (expected YYYY-MM-DD)
Percentage not between 0-100
URL missing protocol (http:// or https://)
Package name doesn't match Android format
How to fix:
Read field label or placeholder for format example
Copy-paste from known good source if unsure
Remove extra spaces or special characters
Match the format shown in error message
What it means: Number entered is outside acceptable range.
Common examples:
Traffic percentage over 100%
Minimum allocation below 5% (Google requirement)
Duration too short (less than minimum)
File size exceeds limit
How to fix:
Check error message for valid range
Adjust value to fall within acceptable limits
Review Google Play requirements if limit seems arbitrary
What it means: Operation took too long and was cancelled.
Common causes:
Slow internet connection
Large file upload
Complex operation (generating many assets)
Server overload
How to fix:
Check your internet connection
Try again in a moment
Break large operations into smaller chunks
Upload smaller files or compress images
What it means: Couldn't establish connection to server.
Common causes:
Internet connection dropped
Firewall or proxy blocking request
PressPlay service temporarily unreachable
DNS resolution failure
How to fix:
Check your internet connection
Try accessing other websites to verify connectivity
Disable VPN temporarily
Try different network (mobile hotspot)
Check PressPlay status page
What it means: Unexpected error occurred on PressPlay's servers.
What to do:
These errors are not your fault
Wait a few minutes and try again
If persistent, report to support with error details
Include what you were trying to do when error occurred
CodeMeaningQuick Fix | ||
400 | Bad Request | Check form inputs for errors |
401 | Unauthorized | Sign in again |
403 | Forbidden | Check permissions |
404 | Not Found | Resource was deleted or URL is wrong |
429 | Rate Limited | Wait 10 minutes before retrying |
500 | Server Error | Wait and retry; report if persistent |
502 | Bad Gateway | Temporary connectivity issue; retry |
503 | Service Unavailable | Check status page; wait for recovery |
504 | Gateway Timeout | Retry operation |
Read the complete error message: Don't just dismiss it; understand what it says
Note the error code: Helps identify category of issue
Check context: What were you doing when error occurred?
Try simple fixes first: Refresh page, sign out/in, clear cache
Look for patterns: Does it happen every time or intermittently?
Check status page: Is there a known issue affecting everyone?
Review recent changes: Did something change right before error started?
Try different environment: Different browser, device, or network
If you need to report an error, collect:
Exact error message and code
Screenshot of error
What you were trying to do
Steps to reproduce the error
When error started occurring
Browser and version
What you've tried already
Activity log entries (if available)
Best practices to avoid errors:
Save work frequently: Don't lose progress due to timeouts
Validate inputs: Double-check data before submitting
Stay within limits: Respect rate limits and quotas
Maintain connections: Keep publisher connections active
Use supported browsers: Stick to Chrome, Firefox, Safari, or Edge
Check requirements: Review Google's specs before creating assets
Monitor status: Subscribe to PressPlay status page notifications
Most errors are temporary or easily resolved. This reference helps you quickly identify and fix issues. When errors persist despite troubleshooting, contact support with detailed information for assistance.
