Persistent TestFlight rejection (Guideline 2.1) - Blank screen despite no API key restriction & build versioning issue

Hello Apple Developer Community,

I'm seeking urgent help for a persistent TestFlight rejection issue. My app is "With Wans Camp Map" (App ID: com.jiro.withwanscampmap).

Problem 1: App constantly rejected for "Guideline 2.1 - App Completeness: app failed to load content" (blank white screen).

• Context: Using Expo (SDK 53) and EAS Build.
• Local Status: When running locally with Expo Go and API key restrictions "None" in GCP, the app loads and displays content (map pins) perfectly. This confirms my API keys and data fetching logic are sound.
• Rejection Reason: Despite setting GCP API key "Application restrictions" to "None (no restriction)", all TestFlight builds are rejected with the same "blank white screen" issue.

Problem 2: Build versioning issue during Transporter upload.

• Context: Even after explicitly setting app.config.js version (e.g., 1.0.1, 1.0.2), ios.buildNumber (e.g., 10, 200), and android.versionCode, Transporter continuously gives an error: "bundle version must be higher than the previously uploaded version '8'".
• Result: App Store Connect consistently shows rejected builds as 1.0.0 (8), even for new submissions. This prevents valid builds from being processed.

Key Questions for Apple Engineers/Experienced Developers:

1. What could cause a TestFlight build to show a blank white screen with no API key restrictions (GCP set to "None"), especially when it works perfectly in local Expo Go? Are there any specific network/bundle ID behaviors unique to the TestFlight review environment that could still block API access?
2. Why does App Store Connect persistently recognize my cfBundleVersion as "8" for version "1.0.0" (even for 1.0.1 builds), despite explicit increments in app.config.js and using autoIncrement: true in eas.json's preview profile? Could there be a stuck state or caching issue on Apple's side for this specific App ID?

I am attaching screenshots of the rejection and my app.config.js and eas.json if needed. Any debugging tips or insights into TestFlight's internal environment/build versioning behavior would be greatly appreciated.

Thank you for your time and assistance.

Best regards, Jiro26