3

I am trying to distribute an app to my Beta Testers using Fabric and whenever I try to archive the build it keeps asking me to distribute older build [1.5.2 (8.0)] whenever I archive a new build the build.

I want to distribute 1.6 (31) and not 1.5.2 (8.0)

Here is a screenshot of my Xcode Organizer

enter image description here enter image description here

Vadim Kotov
  • 8,084
  • 8
  • 48
  • 62
Anuj Rajput
  • 836
  • 9
  • 30
  • I'm having this same problem. Did you find a solution? – jrg Dec 17 '15 at 18:06
  • @jrg Check the answer I posted below. I referred to another question on SA and got it working. Do note that I followed both. Hope it works for you too http://stackoverflow.com/a/34342497/1781918 – Anuj Rajput Dec 17 '15 at 19:17
  • I am not sure if [this](http://stackoverflow.com/a/13620628/1781918) worked for me – Anuj Rajput Dec 17 '15 at 19:19

2 Answers2

10

Often have the same problem – crashlytics is suggesting to distribute an older version when I just archived a newer version.

I found out that there is a hard to find drop down menu to display all archived versions. Select ARCHIVES item and then distribute the desired version.

enter image description here

Lars Blumberg
  • 19,326
  • 11
  • 90
  • 127
  • I have noticed that before and upload all my builds from there only. But my issue was not related to this. It was some archiving issue with Xcode which I have explained in my answer on this thread – Anuj Rajput Apr 22 '16 at 10:29
0

The following answers from this thread helped me resolve this issue

Answer 1

If you're using CocoaPods as well as WatchKit or a Today Extension, there is an open issue on the CocoaPods repo explaining what your problem might be.

The solution for me was to remove the Copy Pod Resources phase from the WatchKit Extension and Today Extension targets under Build Phases. The project compiled and archived as expected once I did this.

Hope this helps someone, this had me stumped for an entire day!

Answer 2

If you export the archive, open it and see /urs/local/include in Products try this suggestion:

In each pod, under Packaging, Private Headers Folder Path and Public Headers Folder Path is set to /usr/local/include. If I clear them then I get a valid archive.

enter image description here

Worked for me after upgrading my React Native app to 0.11.0, Xcode 7 and CocoaPods 0.39.0.beta.4.

Community
  • 1
  • 1
Anuj Rajput
  • 836
  • 9
  • 30