In iOS 10 there is clock_gettime function in system library.
When i compile curl on latest iOS SDK, configure script always define HAVE_CLOCK_GETTIME_MONOTONIC (but i define -miphoneos-version-min=8.0!), that lead to crash on previous iOS versions. Crash looks like EXC_BREAKPOINT (EXC_ARM_BREAKPOINT) on dylib stub_binder. Crash occurred when curlx_tvnow() is called. With HAVE_CLOCK_GETTIME_MONOTONIC it calls clock_gettime, that is not exists on pre-iOS 10.
Is there any way to disable HAVE_CLOCK_GETTIME_MONOTONIC when -miphoneos-version-min less then 10.0?
i have compile the CURL(https://curl.haxx.se/download.html) with adding CFLAGS= CFLAGS + "-miphoneos-version-min=8.0 -Werror=partial-availability" and its working fine for me.
Related
I've developed an iOS app that uses the url(forPublishingUbiquitousItemAt:expiration:) method of Apple's FileManager class. Starting with the first Beta of iOS 13 this function stopped working and now it throws an error, stating "This code has been removed. You should switch off of this SPI". But I can't find anything related to this function neither in the release notes of iOS nor in the documentation for this function, and it even states there that it would be supported on Mac Catalyst 13.0+.
This also has nothing to do with Xcode 10 and 11, as it occurs when the app is built using either one of those versions.
Does anyone of you know more about that? It would be great to get new information on that.
Thanks,
Fabian.
This is fixed in iOS 13 beta 6. Updated today and this error magically disappeared!
Had my mind blown when I saw this error message.
We have an app that is working properly with the UserNotification.framework being linked as required framework in Xcode 9. Everything works smooth here.
Now we are switching to Xcode 10. But there linking this framework as required leads to
dyld: Library not loaded: /System/Library/Frameworks/UserNotifications.framework/UserNotifications
Referenced from: /var/containers/Bundle/Application/1D41BD68-9B88-4D5D-B7AB-0D1C31979964/App.app/App
Reason: image not found
If I switch it to optional push notification (via Intercom) won't work anymore.
What is the reason? How can we fix that? Why is it even working in Xcode 9?
Update #1
using
#import UserNotification
does not fix it
Update #2
Its fixed by importing and using it actually (in AppDelegate.m) like this
UNNotificationRequest* unr = [UNNotificationRequest alloc];
unr = nil;
Why?
It is related to the same issue I have experienced already.
CABTMidiCentralViewController used in Storyboard only working if using code reference
Update #3
More generic question
Xcode sometimes removes linked library
UserNotification SDK is available on iOS 10+, Try to update the deployment Target to iOS 10 +
Can your please try removing the framework and adding that again ? I just created a new project this framework added in Xcode 10 and was able to run in the device without any errors.
Need to check whether device is jailbroken using cordova. I tried the cordova-plugin-jailbreak-detection plugin, but still can open the same in JAILBROKEN Device. then i got .m files from https://github.com/Shmoopi/AntiPiracy. it was working fine till XCode 8. In XCode 9, getting "System keyword is unavailable" error
Any latest plugin/class files to check Jailbroken compatible for latest XCode ?
system call is not available for ios, remove + (int)systemCheck and it should work for you. Also in + (void)killApplication method comment system call
The isJailbroken method performs various check and if the score is >= 3 then it marks it as Jail broken. Now as the system call is not available then we can live without the score of + (int)systemCheck and proceed without it.
I have a minimal working project which if compiled with Xcode 8.3.3 gives me EXC_BAD_ACCESS. The project is a simple VIPER implementation of modules. Swinject is being used to create the module itself along with all the dependencies.
How I solved the problem (or thought I solved):
By removing references of the SwinjectBug directory and re-adding solved the problem a few days ago. However, this is not working anymore.
What still solves the problem:
Compiling and running in Xcode 9-beta with the same iPhone model and iOS version works perfectly. [This observation was probably wrong. Not working all the time]
If I force cast output as! SplashScreenPresenter, the code works fine.
Possible scenarios:
There is a bug in Xcode 8.3.3 which is solved in Xcode 9
But if the above is true, it should have failed for other modules but that is not the case.
Something is wrong in the way I am using Swinject.
You may compile and run the project.
I am using:
iOS 10.3.1 on iPhone 6s 64GB
Xcode 8.3.3
The EXC_BAD_ACCESS occurs in SplashViewController on calling viewIsReady on output
override func viewDidLoad() {
super.viewDidLoad()
output.viewIsReady()
}
Background
I have a fairly detailed (around 2000 lines of swift code) automation framework built with Xcode 7.3 and Swift for our iOS app.
Up till a recent point, I was able to use lldb to build my framework i.e
insert breakpoint and run code up till that point
use po XCUIApplication().debugDescription and expr bla bla to build the logic
repeat
Problem
Pretty much all of a sudden, I now encounter the following error whenever running anything inside lldb's console:
(lldb) po XCUIApplication()
error: <EXPR>:2:1: error: 'XCUIApplication' is only available on iOS 9.0 or newer
XCUIApplication()
^
<EXPR>:2:1: note: add 'if #available' version check
XCUIApplication()
^
<EXPR>:2:1: note: add #available attribute to enclosing instance method
XCUIApplication()
^
<EXPR>:2:1: note: add #available attribute to enclosing extension
XCUIApplication()
^
<EXPR>:10:9: warning: initialization of variable '$__lldb_error_result' was never used; consider replacing with assignment to '_' or removing it
var $__lldb_error_result = __lldb_tmp_error
~~~~^~~~~~~~~~~~~~~~~~~~
Notes
Googling and research has not gotten me anywhere significant.
The one relevant thread I found was in the fastlane project. Unlike that comment, mine is a UI Test target.
Also, the test target's "iOS Deployment Target" is set to iOS 9.2 (in case that helps).
To the extent I remember, I haven't changed anything significantly in recent times.
My device is (and has always been) iOS 9+.
What could be going wrong?
Update 20 May 2016
Some exploration based on the answer below: https://stackoverflow.com/a/37335950/682912
The issue happens only on real devices. Simulators do not face this problem.
On real device (iPhone 6S+, iOS 9.2.1), I did a full reset of Content and Settings. This did not fix the issue.
This is a bug in the debug agent installed on your device. These are bound to the iOS version, so it probably happened when you upgraded your device. Anyway, please file a bug with http://bugreporter.apple.com.
If I'm right about the problem, it should only happen when debugging to the device, not on the simulator. That might allow you a temporary workaround till the bug gets fixed.
Double check your .xcconfig with your test target or any other means that may set your IPHONEOS_DEPLOYMENT_TARGET to lower than 9.0.
Since UITest is only available on iOS9.0 or later, change IPHONEOS_DEPLOYMENT_TARGET to 9.0+ should fix the issue.