AppMaker更换Drive Table为Cloud SQL后无法预览，寻求排查建议

Alright, let's walk through the key troubleshooting steps to figure out why your App Maker preview is failing after switching from Drive Tables to Cloud SQL. I’ve seen similar issues before, so here’s what to check first:

1. Verify Cloud SQL Connection & Permissions #

• Double-check that your App Maker project’s service account (usually in the format [project-number]@cloudbuild.gserviceaccount.com or appmaker-api@[project-id].iam.gserviceaccount.com) has the Cloud SQL Client role assigned at the Cloud SQL instance level. Missing this will block App Maker from accessing the database entirely.
• Confirm your Cloud SQL instance allows connections from App Maker:
  • For public IP setups, ensure App Maker’s IP ranges are added to the instance’s authorized networks.
  • For private IP, verify VPC peering between App Maker’s VPC and your Cloud SQL VPC is configured correctly.
• Test the connection directly in App Maker’s Data > Cloud SQL section by running a simple SELECT * FROM your_table LIMIT 5 query. If this fails, the core connection is the problem.

2. Check Data Model & Schema Compatibility #

Drive Tables and Cloud SQL have subtle data type and behavior differences—misalignments here often break preview:

• Match every App Maker model field’s data type to its corresponding Cloud SQL column (e.g., App Maker String ↔ Cloud SQL VARCHAR/TEXT, Integer ↔ INT, date/time fields must use compatible formats).
• Ensure NOT NULL columns in Cloud SQL are marked as required in App Maker’s data model, and default values are set if the app might create records without providing those fields.
• Validate foreign key relationships: Make sure App Maker model relationships map correctly to Cloud SQL’s foreign key constraints, and that index names/key columns match exactly.

3. Dig Into Preview-Specific Error Details #

• Open your browser’s developer console (F12) when the preview fails—this will show raw error messages that App Maker’s generic error screen hides. Look for:
  • Permission denied: Points to IAM or Cloud SQL authorization issues.
  • Column not found/Invalid data type: Indicates schema mapping mistakes.
  • Connection timeout: Suggests network connectivity issues between App Maker and Cloud SQL.
• Try deploying a test version of the app (not just preview) — sometimes preview uses cached configuration that doesn’t reflect your latest Cloud SQL setup.
• Clear App Maker’s internal cache (go to Settings > Clear Cache in the editor) and your browser cache to rule out stale data.

4. Audit App Logic & Scripts #

Drive Tables had unique behaviors that Cloud SQL doesn’t replicate—your scripts might need updates:

• Replace Drive Table-specific syntax (like using __key__ for record IDs) with standard SQL references to your Cloud SQL primary key column.
• Check server-side scripts that handle record creation: Cloud SQL uses auto-increment columns or UUIDs for IDs, unlike Drive Tables’ auto-generated keys. Make sure your scripts account for this difference.
• Test individual components (like forms or data-bound widgets) in preview to isolate which part of the app is triggering the error.

内容的提问来源于stack exchange，提问作者alep