I'm using the same Xcode project to build the same App on IOS and OSX. I'm new as OSX developer.
For this Application I'm sharing code to send HTTPS request to a server using NSURLConnection. It works perfectly well with IOS but with OSX I have some troubles.
In OSX, when the request is sent I have an exception in NSURLConnectionLoader (see screenshot) that never happen in IOS. In Xcode if I click many times "Continue" on the debugger the request is sent and I'm receiving correctly the response from the server.
Once the first request has been sent the following requests are sent without error! I have no idea how to progress on this issue.
Any idea is welcomed! I was wondering if it could be due to issue with entitlement and/or conflict with IOS App because it's managed in the same Xcode project.
Regards,
Sébastien.
This can happen on OSX if you have an All Exceptions Breakpoint set for the project. For some reason any HTTPS address will throw an internal exception that will cause this. If you remove the breakpoint it should resolve your issue.
If you run rather than debug, does it just work?
Related
This issue happens only in iOS 11 But works fine in other versions
So this question is not a duplicate and need to know what could be the cause
Issues details:
I am using a 3rd party library(private) & the issue happens in it.
When we debug the results from the library call we found the following issue log,
The certificate for this server is invalid. You might be connecting to
a server that is pretending to be
“DOMAIN.com” which
could put your confidential information at risk
But if the issue occurs in iOS 10 and below it would be fine and would have decided its common issue. But since it occurs only in iOS 11 I wonder why, Any suggestions or solutions please ?
We are developing app for iOS and Android and we are using Ti.Gelocation to getCurrentPosition and then set the Region of the MapView of ti.map module.
The app is already on marketplace and downloaded, so we are developing an important upgrade with this new feature. We dont't have problem with Android platform, but with iOS version of the app we get a several error invoking Ti.Geolocation module
The error on iOS 9.x on iPad and iPhone (we have no test on iPod) is:
-[__NSCFString containsObject:] unrecognized selector sent to instance 0x1463d500 at GeoView.js (line xxxx)
This error happens with the project with it.vocami.vocamiapp app-id, in the test project (ap-id=it.vocami.vocamitest) that we use for research and test of new features, no error happens and all run good. When we add at every level of our code (in the first row too), for example, Ti.Geolocation.locationServiceEnabled, in the main vocamiapp project, we get the error.
We have tried all we could think but at the end, if we change the app-id, the code runs otherwise we get the error. We cannot change the app-id because we need to update our published app.
We are developing with AppceleratorStudio version 4.5.0.021602170281 and Ti SDK ver 5.2.0GA on Mac OS X 10.10.5.
I just recently was "hit" by the fact that when I made my app ready for Google Play I use a specific key/user to sign it with. That behaves differently from just running it locally on the phone.
I had to make sure that I had registered two certificates with Google's API in the developer console. It didn't give me exactly the message that you show - but wouldn't show the map with a location. And the way I read the location prior to showing it on the map led me in the wrong direction looking at permissions on Android first :-)
/John
i created an hybrid application that should connect to the MFP and consume data.
When i try to connect to the Desktop Browser Application everything is fine and the app works. Same behaviour when i try the Mobile Web Application. BUT when i try to connect with the mobile native iOS application i could not connect and receive the following error (in the console):
2015-11-12 17:22:15.031 APPXYZ[6072:3089110] [FATAL] [NONE] Uncaught Exception: TypeError: WLJSX.Ajax.WLRequest.setConnected is not a function. (In 'WLJSX.Ajax.WLRequest.setConnected(false)', 'WLJSX.Ajax.WLRequest.setConnected' is undefined) at (compiled_code):3871
My specs:
MFP version 7.1.0.00.20151107-1653
Xcode 7.1.1
iOS deploy target 8.0
Transport security protocol is deactivated (Allow Arbitrary Loads -> YES)
I cannot confirm this claim.
Using the following, I create a blank new Hybrid app with the iPhone environment, that calls the WL.Client.connect method in wlCommonInit() and displays an alert with "success" or "failure" accordingly. I got "success". No errors in the Xcode Console.
Xcode 7.1.1
IBM MobileFirst Platform Studio 7.1.0.00-20151107-1647
If you are doing something different in your project, do let us know...
The solution of my problem was that i change the init calling sequence of my app. I called the wl specific functions to early. After changing the sequence my app runs perfectly.....
thx 4 help :)
I am using AFNetworking 1.2 library in my app. When I have iOS6 as a base SDK everything works fine, but if I change base SDK to iOS7, then receiving an error in some requests(not all) stating that - "The network connection was lost".
I am not able to find out the cause of the issue, also there is no pattern for this issue as all requests are not failing.
Is there something change in the iOS7 SDK which is causing this issue?
After analyzing issue for 2-3 days, found the root cause of the issue. In response header getting some field which sdk not able to handle.
As others have said, for iOS7, you'll want to upgrade to a newer version of AFNetworking (2.x)
I just downloaded the lukeweber version of webrtcjingle, which I believe is just a branch of the google one.
I change the server and account setting on the demo and run it. It was able to log in and send/receive messages. However, When I tried to logout. The app crash.
I had a little debug on it, and found out the line of code that crash was in file txmppump.cc, function:
void TXmppPump::WakeTasks() {
talk_base::Thread::Current()->Post(this);
}
Does anyone have an idea what the problem is? I noticed that there is a fix on disconnecting problem issued caused by a race problem on the repo:
github bug list
However, I compared my code to the fixed version. They are the same. So I dont know if they are related or not.