Step 6: Submit for Build

This is the final step before WhautoChat builds your apps. You'll gather everything you've prepared and submit it to the WhautoChat team.

Time Required

30 minutes to package and submit

What You're Submitting

You'll submit three categories of items:

1. Visual Assets (from Step 5)
2. Apple Credentials (from Step 3)
3. Google Credentials (from Step 4)
4. OneSignal Configuration (from Step 2)

Pre-Submission Checklist

✅ Visual Assets

• App Icon (1024 x 1024 px, PNG)
• App Icon Foreground (1024 x 1024 px, PNG)
• Splash Screen Light (2732 x 2732 px, PNG)
• Splash Screen Dark (2732 x 2732 px, PNG)
• App Name decided
• Bundle ID decided

✅ Apple Credentials

• Distribution Certificate (.p12 file)
• Certificate password
• Provisioning Profile (.mobileprovision file)
• App-Specific Password OR API Key
• Apple Developer Account email
• Team ID
• Bundle ID registered in Apple Developer Portal

✅ Google Credentials

• Upload Certificate (PEM format) OR Keystore file
• google-services.json file
• Firebase Server Key
• Package Name (same as Bundle ID)
• Keystore passwords (if applicable)

✅ OneSignal Configuration

• OneSignal App ID
• OneSignal REST API Key
• iOS APNs configured in OneSignal
• Android FCM configured in OneSignal
• Backend configured with OneSignal credentials
• Backend installation re-run

✅ URLs and Information

• Privacy Policy URL (live and accessible)
• Support URL (live and accessible)
• Marketing URL (optional)

Critical: Backend Configuration

Must Complete Before Submission

Your WhautoChat backend must be configured with OneSignal credentials before submitting for build. This is non-negotiable.

Verify Backend Configuration

1. SSH into your WhautoChat server
2. Check your .env file contains:

   ONE_SIGNAL_APP_ID=your-onesignal-app-id
   ONE_SIGNAL_API_KEY=your-onesignal-rest-api-key

3. Verify installation was re-run after adding these credentials
4. Test that push notifications work from your backend

If not configured: Go back to Step 2: OneSignal Configuration and complete the backend setup section.

Organize Your Submission

Create Folder Structure

whautochat-mobile-build-[YourCompanyName]/
├── assets/
│   ├── app-icon.png
│   ├── app-icon-foreground.png
│   ├── splash-light.png
│   └── splash-dark.png
├── ios/
│   ├── distribution-certificate.p12
│   └── provisioning-profile.mobileprovision
├── android/
│   ├── upload-certificate.pem (or keystore.jks)
│   └── google-services.json
└── app-info.txt

app-info.txt Template

App Name: WhautoChat Business
Bundle ID: chat.whauto.app
Version: 1.0.0

Short Description (80 chars):
Professional WhatsApp Business messaging and automation platform

App Category:
iOS: Business
Android: Business

Target Audience:
Business users, customer support teams, sales teams

Special Notes:
[Any special requirements or notes for the build team]

Compress Your Files

1. Select all files and folders
2. Create a ZIP archive
3. Name it: whautochat-mobile-build-[YourCompanyName].zip
4. Verify the ZIP file is complete and not corrupted

File Size

The ZIP file should be around 5-20 MB depending on your splash screen images.

Submit to WhautoChat

Email Submission

To: [email protected] (or your designated contact)

Subject: Mobile App Build Request - [Your Company Name]

Email Template:

Hello WhautoChat Team,

I'm ready to submit my whitelabel mobile app build request.

Company Name: [Your Company Name]
Contact Person: [Your Name]
Email: [Your Email]
Phone: [Your Phone Number]

App Details:
- App Name: [Your App Name]
- Bundle ID: [Your Bundle ID]
- Target Launch Date: [Optional]

Backend Configuration:
✓ OneSignal credentials configured in backend
✓ Backend installation re-run
✓ Backend URL: [Your Backend URL]

Please confirm receipt and let me know if you need any additional information.

Thank you!

Best regards,
[Your Name]

Attach: Your ZIP file

Alternative: Secure File Transfer

If your ZIP file is too large for email (>25 MB):

1. Upload to Google Drive or Dropbox
2. Set sharing permissions to "Anyone with link can view"
3. Include the download link in your email
4. Set link to expire in 7 days for security

What Happens Next

1. Acknowledgment (Within 24 Hours)

WhautoChat will confirm receipt of your submission.

2. Review (1-2 Business Days)

The team will review all submitted materials and verify:

• All required files present
• Credentials are valid
• Assets meet specifications
• Backend is properly configured

3. Clarifications (If Needed)

If anything is missing or incorrect, you'll be contacted with specific requests.

4. Build Process (1-3 Business Days)

Once everything is approved, WhautoChat handles the complete build process:

What WhautoChat Does:

Day 1: Configuration & Build

• Configure build environment with your Bundle ID and Package Name
• Integrate OneSignal credentials for push notifications
• Set up Apple certificates and provisioning profiles
• Configure Google Play app signing
• Add your app icons and splash screens
• Build iOS app (IPA file)
• Build Android app (AAB file)
• Sign both apps with your credentials

Day 2: Quality Assurance

• Test app launches successfully on iOS and Android
• Verify splash screens and icons display correctly
• Test push notifications work on both platforms
• Check login and core functionality
• Test on multiple device types and OS versions
• Verify deep links work correctly
• Check for crashes or critical bugs

Day 3: Final Delivery

• Package IPA and AAB files
• Generate build documentation
• Create secure download links
• Send delivery email with instructions

What You Get:

• Production-ready IPA file (iOS) - signed and ready for App Store
• Production-ready AAB file (Android) - signed and ready for Play Store
• Build information document
• App store submission guide

5. Delivery

You'll receive:

• IPA file (iOS) via secure download link
• AAB file (Android) via secure download link
• Build documentation
• Submission instructions

After Submission

What You Can Do

While waiting for the build:

1. Prepare store listings - Start working on Step 7: Prepare Store Listings
2. Take screenshots - If you have a similar app, prepare screenshots
3. Write descriptions - Draft your app store descriptions
4. Plan launch - Prepare your launch strategy

What You Should NOT Do

• Don't change your Bundle ID or Package Name
• Don't modify certificates or provisioning profiles
• Don't change OneSignal configuration
• Don't make major backend changes

warning

Any changes to credentials or configuration after submission will delay the build process.

Common Issues

"Email bounced back"

Solution: Check the email address. Try alternative contact method if provided.

"ZIP file too large"

Solution: Use Google Drive or Dropbox to share the file. Compress images if needed.

"Backend not configured"

Solution: Go back to Step 2 and complete the backend OneSignal configuration.

"Certificate expired"

Solution: Generate new certificate in Apple Developer Portal and resubmit.

Submission Checklist

Final verification before sending:

• All assets included and properly named
• All credentials included
• app-info.txt file complete
• Backend OneSignal configuration verified
• URLs tested and accessible
• ZIP file created and tested
• Email drafted with all information
• Contact information provided
• Ready to wait 1-3 business days for build

Need Help?

If you're unsure about anything:

1. Review the specific step guide (Steps 2-5)
2. Check the troubleshooting sections
3. Contact WhautoChat support before submitting
4. Better to ask questions now than delay the build

Next Step

After submitting, while you wait for the build:

Step 7: Prepare Store Listings

Start preparing your app store screenshots, descriptions, and other listing content.

---

Timeline Reminder

Phase	Duration
Your submission	30 minutes
WhautoChat acknowledgment	24 hours
Review and clarifications	1-2 days
Build process	1-3 days
Total	2-5 days

Be patient - quality builds take time! 🚀