- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-11-2020 02:01 PM
I just spent two days rebuilding an application because it would not load cleanly when importing it from github. In github, I renamed my existing repo and created a new, empty repo with the old name. In Studio, I did Link to Source Control and pointed to the new repo. I got:
Unable to export. Remote repository contains a different application
What would make Studio think this when there are no files in the repo?
Solved! Go to Solution.
- Labels:
-
Scoped App Development
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-11-2020 02:47 PM
Found a video with the answer. Go to sys_repo_config.list
, delete the repo connection and link to source control again.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-11-2020 02:32 PM
Unclear what I did fiddling with this, but now Studio thinks it is linked to the github repo. If I try to commit changes, I get:
Repository has changes that are not applied yet. Apply changes from source control then retry this action.
Then if I try to apply remote changes from source control, I get:
Repository does not contain an Application file to import
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-11-2020 02:47 PM
Found a video with the answer. Go to sys_repo_config.list
, delete the repo connection and link to source control again.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-12-2022 12:18 PM
Excellent! Thank you Chris. This did the trick for me!
Cheers,
M
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-10-2023 01:52 AM
Hi Cbarlock
It's my understanding that the error is being triggered by more than just the presence of files. There could be metadata or references within the application that are still pointing to the old repository. May I please ask you to examine the application's settings and references thoroughly. Clearing any local caches related to Studio or the source control integration might also help resolve the issue, as cached data can sometimes lead to conflicts.
For a more comprehensive and efficient resolution, I can suggest you Exalate. I have been using it for quite a while and it instantly jumped in my thoughts reading this post. It is an integration solution that works super fast in my opinion.