5

I uploaded a version of my app – this error pop ups and I dont have any changes from the Google Maps portion of my app. On my first upload, there was no problem.

Pang
  • 9,564
  • 146
  • 81
  • 122
user1969245
  • 91
  • 1
  • 1
  • 5

7 Answers7

6

Just remove the embed frameworks build phase from your extension.

Click on extension in target section -> Build phases -> remove the embed pods frameworks

See attached picture:

enter image description here

Vijay Sharma
  • 1,046
  • 9
  • 19
1

This issue is probably Apple's iTunesConnect side of the problem. see my question: ITMS-90451:CFBundleIdentifier Collision Error

I also encountered the same problem in the submission of the application using the Qt framework. I have submitted a report in https://bugreport.apple.com/. Something I will even write if there is a reply from Apple.

Community
  • 1
  • 1
Sawatsu Kengo
  • 81
  • 1
  • 7
  • In 4/17 I received from Apple Technical Support. However, the problem did not resolve at all. I wrote in detail the progress of this topic in Mac DeveloperForum. Please look at the following URL. https://devforums.apple.com/message/1127790#1127790 – Sawatsu Kengo Apr 21 '15 at 06:44
  • Add in 4/29 is below. This error was resolved!! Please answer refer to my question. http://stackoverflow.com/questions/29588606/ – Sawatsu Kengo Apr 29 '15 at 07:19
0

I am wondering if iTunes Connect is having a temporary issue. I have the same exact error, now with a different third party library

byedissident
  • 181
  • 2
  • 4
0

I Solve the problem. I just deleted the 3rd party framework. Then add it again. I don't why it cause this but it works.

user1969245
  • 91
  • 1
  • 1
  • 5
0

Frameworks Signing set to None and Don't Code Sign.

Build Phases - Copy Files - Code Sign On Copy Enabled

David Yuan
  • 1
0

This issue is either iTunesConnect issue or Cocoapods.

When you archive and submit the App, you get this “CFBundleIdentifier Collision Error” because iTunesConnect is considering info.plist of one of pod dependency not your Watchkit App or its parent App.

In our case, it was considering Google Maps and Instabug's info.plist file.

Solution : To solve this issue we deleted all the values of info.plist from our pod dependency. Clean archive and successfully submitted.

GoogleMap iOS SDK contains info.plist on following path : GoogleMapSDK -> Resources -> GoogleMaps.bundle -> info.plist

Google Map info.plist

Screenshots of Errors :

Instabug

Google Maps

Arsalan
  • 150
  • 1
  • 11
  • Can you elaborate a bit more on the 'key/value pair' from your 'pod dependency' please? I'm a bit lost as to what you mean. – Tony Apr 22 '15 at 01:03
  • By key/value pair i mean, info.plist of your pod dependency. In Google Map SDK -> Resources -> GoogleMaps.bundle -> info.plist. Delete values in info.plist of your pod dependency. – Arsalan Apr 22 '15 at 17:17
  • Have also added the screenshot now. – Arsalan Apr 22 '15 at 17:22
  • Thanks! So you essentially submitted an app with an empty Info.plist file inside your pod dependency? – Tony Apr 22 '15 at 18:22
  • info.plist under pod dependency is actually useless, Our submitted Watchkit App was approved by Apple Yesterday. – Arsalan Apr 22 '15 at 19:22
  • Okay, thanks for the information! Congrats on the approval :) – Tony Apr 22 '15 at 19:26
0

If you have more than one target in your app and a Framework used in more than one target, you don’t need to embed it in all targets. Just embed it in one target and set the property to "Do not embed" for other targets. Note that some targets like NetworkExtensions, should not embed some dependencies, therefore the Main target is the preferred target to embed the Framework which caused the problem.

Mahdi Moqadasi
  • 2,029
  • 4
  • 26
  • 52