Best solution for No Schema problem in Xcode 4 after refusing merge git branches

Got a "No Schema" problem after merging a conflict problem

Auto merge SampleProject.xcodeproj / project.pbxproj CONFLICT (content): merge conflict in SampleProject.xcodeproj / project.pbxproj Auto merge error; fix conflicts and then record the result.

Definitely, I did some unsuccessful operations when merging conflicts. The question is, is there a better solution to fixing the "No circuit" problem in this case.

+7
source share
5 answers

When " No Pattern " is displayed on the chart, click

No Scheme Manage Scheme then click Autocreate Schemes Now

+31
source

A similar question. Closed my projects, left, and then opened Xcode again, and my circuits returned.

+2
source

I found that the highest answer did not work for me, so I thought I would post my usual approach here - since I just had to solve this problem:

We know the problem - the error is actually pretty clear on this problem:

Auto-merge SampleProject.xcodeproj / project.pbxproj CONFLICT (content): Merge conflict into SampleProject.xcodeproj / project.pbxproj Auto-merge error; fix conflicts and then record the result.

We have a conflict in the project.pbxproj file.

If he said “Conflict in appDelegate.h”, we knew exactly what to do, but the fact that the project will not compile seems more alarming than a normal conflict - that’s what it really is.

So how can we fix this conflict?

  • First go to the project file
  • Right click xcodeproj file
  • Click Show Package Contents

enter image description here

  1. Double-click the project.pbxproj file (the one specified in the conflict error)

enter image description here

  1. Finally, resolve conflicts as usual. It takes a little thought - it’s worth reading and trying to understand what is happening. Usually, although it’s quite obvious that you need to save:

enter image description here

The above is an example of how conflicts will look.

Once you find all the conflicts in this file, just save and reload the project. The schema must be returned and the project works.

Note: As mentioned above, some thoughts are needed when resolving conflicts. Usually they will be very light (just remove the conflicting lines), but sometimes you need to fix some code. If you see the example below, the file was damaged and needed to be fixed:

enter image description here

The fix required in this example was:

  path = DetailModels; sourceTree = "<group>"; }; 

This code needs to be added and can be generated from the code in the above areas.

+1
source

I have the same problem. After some testing, I opened Xcode and went to the problem navigator and opened the conflicting files as source code, then started searching with the keyword <<<<<<< HEAD , then started fixing conflicts. After that, the goal appeared :)

0
source

This is how I solved my No Circuit dilemma. After several hours of trial and error, I tried to delete xcode.workspace, where there were no hav schemes and cd, in a folder in which the workspace was simply deleted, than I installed pod to reload the workspace. And then all my projects and a folder appeared.

It was also important to go to the settings target-> build and set the FrameWork search paths for debugging and release ($ inherited) and $ (SRCROOT) before deleting the workspace.

Hope this helps someone!

0
source

All Articles