Existing AI Studio app lost GitHub sync after connecting a second AI Studio app part 2

Hello Google AI Studio Team,

I need help with a GitHub synchronization problem affecting an existing Google AI Studio Build project.

My original AI Studio project was previously synchronized normally with:

GitHub repository: “asramastapa-stack/JSON-tes-masjid”
Branch: “main”

The problem started after I created a second/new AI Studio app and connected that new app to another GitHub repository:

“asramastapa-stack/SIPONDOK”

The new app successfully synchronized with GitHub.

After connecting the second app, my original AI Studio project stopped being able to check its GitHub sync status.

The original project now shows:

“Failed to check GitHub sync status”

I have already tried Try again, but the error remains.

To test whether the second app was causing the problem, I disconnected the GitHub connection from the new “SIPONDOK” app. However, the original “JSON-tes-masjid” project still shows the same error.

The original GitHub repository still exists and has not been deleted, renamed, or replaced.

I have also NOT disconnected the original AI Studio project from GitHub because I do not want to lose its existing repository binding.

Current situation

  • Original AI Studio project → “JSON-tes-masjid” → sync fails
  • Branch → “main”
  • New AI Studio project → “SIPONDOK” → previously synchronized successfully
  • New project’s GitHub connection has now been disconnected
  • Original project still shows “Failed to check GitHub sync status”
  • “JSON-tes-masjid” still exists on GitHub
  • I have already submitted feedback through Google AI Studio and provided a screen recording

Could the Google AI Studio team please investigate the GitHub binding/synchronization state of my original AI Studio workspace?

I would like to restore synchronization between the existing AI Studio workspace and the existing:

“asramastapa-stack/JSON-tes-masjid”

without creating a new repository or replacing the existing AI Studio workspace.

I can provide the Applet ID and additional screenshots or screen recordings privately if required.

Thank you.

Since the repo’s still there on GitHub, the main thing is not to lose the AI Studio workspace while this gets sorted.

  1. I’d export the code as a ZIP from AI Studio first, as a backup.
  2. Then look on GitHub, which changes nothing: Settings > Applications > Installed GitHub Apps (if asramastapa-stack is an organization, it’s the org’s Settings > Third-party Access > GitHub Apps). Click Configure next to Google AI Studio. If Repository access is set to “Only select repositories”, check that JSON-tes-masjid is still listed. It’s worth a look because this started right when you connected another repo.
  3. If it’s missing, add it back and press Try again in AI Studio. That’s a small change on GitHub, but it only gives access back.
  4. If it’s listed and sync still fails, one or two people in this older thread fixed a different GitHub error in Build mode by revoking Google AI Studio under Authorized GitHub Apps and reconnecting. Others said it didn’t help, and I can’t promise it keeps your repo link, so I’d leave that until Google replies.

If nothing works, you can keep GitHub current by hand: clone the repo, make a new branch, run git rm -r -q . to clear the tracked files, then unzip the export so its files sit at the top of the folder (not inside a subfolder) and run git add -A. Check git status before you commit: if a .env file with a real key is staged, add it to .gitignore, then run git rm --cached .env and git add .gitignore so the key stays out and the ignore rule goes in with the commit. Then commit and push the branch.

Hello @Asrama_Parabek ,

Please try the below steps:

  • Uninstall the Google AI Studio app from your installed GitHub Apps on GitHub as described in Reviewing and modifying installed GitHub Apps (uninstalling the app only removes the app installation and does not delete or modify your existing project, repository history, or deployment).
  • Open your project in Google AI Studio and select “Sign in to GitHub to continue” to complete a fresh installation and authorization flow.