starting from today my Crashlytics (icon on the system bar) is automatically shutting down after archiving Swift app from Xcode so uploading the app on the server is not possible anymore. I use Crashlytics for almost half a year and just yestardeay everything works fine. I have rebooted the system and Xcode but it didn't help. I use Xcode 6.2.
It seems that there were some update lately in the Crashlytics software so I uninstalled and installed the main Crashlytics.app once again but with no effects.
Asking for help.
Regards,
Michał
I installed Fabric which now integrates Crashlytics and other tools. After reconfiguration of the project (changes in the run script and AppDelegate according to Fabric live plugin) everything works with no problems.
Regards,
Michał
Related
I am using a mac running on High-Sierra, I have installed MacOS server and xcode. On the sidebar of macOS services. Xcode is suppose to be shown like this:
But on my macOS server, it does not show it.
Can anyone help me with this?
The problem is related with the last upgrade "Xcode 9".
At WWDC 2017, Apple announce something that made almost every iOS developer smile, session on ‘What’s New in Signing for Xcode and Xcode Server’. It’s hard to explain, how easy it become to perform Continuous Integration for Apple platforms especially iOS and macOS using Xcode 9 and Xcode Server.
More details about WWDC 2017: Click Here
Xcode Server no longer need macOS Server app, it’s now built inside Xcode.
For continuous integreation, plase following this link.
Good coding!
I accidentally deleted some crashlytics files out of my xcode project and now my app wont launch.
Header 'Crashlytics.h' not found
Could not build Objective-C module 'Crashlytics'
How can I reinstall crashlytics? Fabric still thinks it is installed.
Lots of people are facing the same issue (myself included). Here is a support thread over at twitter with a few suggestions.
Link to twitter support thread
By going through the installation process again I was able to reinstall it.
The content assistant is not working.
I'm working on OSX, Titanium Studio, iOS & Android mobile app and have tried the following:
Installing the following SDKs: 3.2.0, 3.2.1, 3.3.0.
Tried reverting between those versions.
Checked the Project Natures (mobile - primary, mobile module, are checked).
Tried every option on the Project Build Path.
Of course tried to build the project again and again.
Check the content assistant preference both in the main preference and in the project properties.
Are the any more suggestions?
I believe this is a bug in the 3.2.0GA SDK (3.2.1 and 3.3.0 are not official releases yet). As far as I have heard it is known and should be fixed in the next SDK update. Only question is when this update will be out.
You can get content assist back by reverting to 3.1.3GA, but that doesn't help you much if you need features from 3.2.0GA.
EDIT:
The issue is described in this JIRA-ticket and as it mentions should be resolved in the upcoming 3.2.1 release.
I just upgraded to xCode 4.3 and used it to generate a new revision of an iPad app about 50 beta testers have been using for several months. I distributed the beta app through TestFlight as usual.
Most testers upgraded with no problem, but several testers are getting the TestFlight message "You have not permitted this device to install this build" when they try to install the new rev. I've never seen this message before. Their iPad UDID is definitely in the build's embedded.mobileprovision file and everything was working working fine with the prior revision.
What am I -- or the testers -- doing wrong and how do we correct it?
Hi i experienced the same and it seems that you must generate your mobile provisioner profile from Xcode(instead of Apple dev site for example) and you should update your App permissions (TestFlight) with this same provisioner profile that you just generated on your machine so basically the machine that generates and archive the apps using Xcode must generate the provisioner profile and then you should update your testflight app permissions with this file.
Does that make any sense?
Hope this works for you testflight is really nice to use, i faced same problems with all of my apps and hardware devices (testers all around the world)
Thanks
Turns out this is apparently a bug in Testflight. I tried to resolve the issue through their support forum and multiple emails with no real answer. I did not want to switch services as my testers knew the Testflight system well. But eventually switched to Diawi. My testers were able to install the app using Diawi with no problems.
I have a problem with an app that works perfect on my iPhone 4, and on my 3Gs but both are on iOS 4. BUT, when a colleague installed it on his 3G with 3.1.2 on it... it crashes on startup.
Is there someway I can test to install the app in a 3.1.2 simulator of some kind?
He didn't send me his crash logs yet.
Best regards,
Paul Peelen
I haven't done this for the simulator, but you can find links for the old SDKs here:
http://chris-fletcher.com/2010/08/28/howto-install-iphone-sdk-2-0-3-1-for-xcode-3-2/
You should be able to install the old simulator SDKs and have them show up in the simulator menu.
Dealing with multiple SDKs has proved to be extremely painful in my experience. If you end up installing an old SDK, I'd recommend you install it in a separate "Developer" folder.
In my opinion, the best way to deal with 3.x debugging is to get your hand on an old iPod touch with 3.x installed. You can get one for pretty cheap from a local classified ads site and it really makes 3.x debugging a lot easier.