Usually, initializing ITLibrary works like a charm.
But when calling
NSError *error = nil;
ITLibrary *library = [ITLibrary libraryWithAPIVersion:"#1.0" error:&error];
on a customer's machine, I get a The operation couldn’t be completed. (OSStatus error 7011.) error message.
Does anybody know what that means and how to fix it?
This is on macOS 10.15.7, after using Migration Assistant, i.e. moving from an older machine.
The issue was eventually resolved.
Since it is very unlikely that one comes up with the solution, I'm going to post it here:
There was a different issue where an iPhone wasn’t connecting to Finder. A level 2 tech Apple support person suggested to open the TV app and the Music app. Opening both apps somehow fixed both problems.
Related
When I open in Google Drive an error appears:
There was an error loading this notebook. Ensure that the file is accessible and try again.
A network error occurred and the request could not be completed.
https://drive.google.com/drive/?action=locate&id=1HokQj5jSvoeblc3dOr4A_iLnDGN377dZ&authuser=1
Failed to fetch
TypeError: Failed to fetch
When I try to download via colab.research.google.com, an error appears:
A network error occurred and the request could not be completed.
GapiError: A network error occurred and the request could not be completed.
at GG.hy [as constructor] (https://colab.research.google.com/v2/external/external_polymer_binary.js?vrz=colab-20190311-085300-RC00_237811388:1345:363)
at new GG (https://colab.research.google.com/v2/external/external_polymer_binary.js?vrz=colab-20190311-085300-RC00_237811388:1564:363)
at za.program_ (https://colab.research.google.com/v2/external/external_polymer_binary.js?vrz=colab-20190311-085300-RC00_237811388:1652:331)
at Ba (https://colab.research.google.com/v2/external/external_polymer_binary.js?vrz=colab-20190311-085300-RC00_237811388:509:336)
at za.throw_ (https://colab.research.google.com/v2/external/external_polymer_binary.js?vrz=colab-20190311-085300-RC00_237811388:508:402)
at Da.throw (https://colab.research.google.com/v2/external/external_polymer_binary.js?vrz=colab-20190311-085300-RC00_237811388:510:248)
at c (https://colab.research.google.com/v2/external/external_polymer_binary.js?vrz=colab-20190311-085300-RC00_237811388:519:79)
At the same time, the examples provided by Colab, for example, colab.research.google.com/notebooks/bigquery.ipynb are working fine.
consider restarting your browser.
I get a similar problem using colab with firefox sometimes. Same initial message:
There was an error loading this notebook. Ensure that the file is accessible and try again. A network error occurred and the request could not be completed.
Then colab gets stuck, and won't open any files at all. Closing and restarting the colab tab does not clear the problem.
Eventually I discovered that restarting firefox fixes it for me.
I realise that this is too late to help the OP, and it may not be quite the same problem anyway, but when I first hit the issue myself I couldn't find any online help for it, so now I've got an answer I wanted to share.
I get a similar problem using colab with any app and used a vpn proxy and it worked.
Remove all the cookies and refresh the tab, it worked for me.
My Node Red application in IBM BlueMix is repeatedly crashing - once an hour - with no real error message other than "exited with status: 1."
How can I troubleshoot this issue?
Is there someone from IBM BlueMix support that monitors this that could take a look?
I looked at my logs and there's nothing in there that really says what's going on.
Edit per requests:
The regular log for "OUT/ERR" is scrolling so fast with HTTPD logs that I can't get it to copy/paste. Filtering to "ERR" Channel the only thing I see is below. I believe this is an error which occurs during deploy when the application restarts.
[App/0] ERR js-bson: Failed to load c++ bson extension, using pure JS version
My Node Red application is gathering data from Wink, LIFX, and other IoT services and compiles them together into a Freeboard dashboard.
Caught crash on screenshot here -- not enough cred to post images so it'll only post as a link
The zlib error was fixed in the 0.13.2 Node-RED release (that shipped 19/02/16).
If you re-stage your application is should pick up the new version of Node-RED
You can re-stage the application using the cf command line management application:
cf restage <app name>
My Mac application in Xcode has recently begun exhibiting strange symptoms when attempting to access iCloud. There haven't been any changes to my provisioning profiles, code signing identities, etc.
However, when running this code:
id token = [fileManager ubiquityIdentityToken];
NSLog(#"Token is: %#", token);
NSURL *iCloudURL = [fileManager URLForUbiquityContainerIdentifier:nil];
NSLog(#"iCloud URL is: %#", iCloudURL);
The output is:
2013-10-28 08:17:12.372 MyApp[21101:303] Token is: (null)
2013-10-28 08:17:12.373 MyApp[21101:303] iCloud URL is: (null)
Which I find extremely strange, especially considering I am actually signed into iCloud on this machine. To be sure, I ran a quick test with Calendar, adding an event on an iPhone and ensuring that it showed up on the Calendar on my Mac.
But I was under the impression that [fileManager ubiquityIdentityToken]; would return whether the user was logged into iCloud, regardless of whether your entitlements, code signing, etc. was properly configured - indicating that it's less an issue on my end, and more an issue of the system's ability to return this value.
I have tried logging out (and back in) to iCloud, and have ensured that "Documents & Data" is enabled in the iCloud settings.
This was resolved by upgrading from the original Mavericks GM (build 13A598) to the official release (build 13A603.)
I'm setting up In-App purchasing for my Mac App. I currently am able to get the product from iTunes Connect, and even request a purchase. I'm pretty stumped with this error message, and am really hoping someone has been here before and can offer some assistance.
I am getting the (very helpful) localized error: Transaction error: Unknown Error.
I've included the two images of successful Mac App Store authentication, and error message. All I'm able to figure out is that the failedTransaction is being called from the SKPaymentTransaction.
Here's what I did. Archive in Xcode. Then distribute -> mac installer -> double-click .pkg file & install.
That seems to download the _MASReceipt and all is well when including
if(![[NSFileManager defaultManager] fileExistsAtPath:[[[NSBundle mainBundle] appStoreReceiptURL] path]]) {
NSLog(#"to get sandbox receipt, the app must be launched from outside xcode");
exit(173);
}
I am using AFNetworking to connect from an iOS v6.0 app to my local Cold Fusion 8 server, not on the same machine but on the same network and the connection times out. When I use an external public server it works fine.
I have tried the connection via IP address and it doesn't work.
I have tried an entry in the hosts file assigning a domain name to the IP address and this doesn't work either. Please see the error below.
I can however connect via a web browser just fine.
Also, the server side files are exactly the same. Versions of Cold Fusion are the same. The only difference that I can find are the public server is Win2003 with IIS6 and the local server is Windows7 with IIS7.
Any thoughts on why this would not work on a local network. Makes local development kind of difficult.
Here is the relevant code:
// load params
NSMutableDictionary *myParams = [[NSMutableDictionary alloc] init];
[myParams setValue:#"Hello" forKey:#"Parameter1"];
[myParams setValue:#"There" forKey:#"Parameter2"];
// Load the base URL into a URL object
// Changing this to an external public server works fine
NSURL *baseURL = [NSURL URLWithString:#"http://www.mylocalmachine.com/"];
// Create HTTP client and init with base url
AFHTTPClient *myHttpClient = [[AFHTTPClient alloc] initWithBaseURL:baseURL];
// POST request to path with the parameters
NSMutableURLRequest *myRequest = [myHttpClient requestWithMethod:#"POST" path:#"myfile.cfm" parameters:myParams];
// Block response from the HTTP client request and pass it back to the calling object
AFJSONRequestOperation *myOperation = [AFJSONRequestOperation JSONRequestOperationWithRequest:myRequest
success:^(NSURLRequest *mySuccessRequest, NSHTTPURLResponse *mySuccessResponse, id mySuccessJSON)
{
// PROCESS THE SUCCESS RESPONSE;
}
failure:^(NSURLRequest *myFailureRequest, NSHTTPURLResponse *myFailureResponse, NSError *myFaliureError, id myFailureJSON)
{
// PROCESS THE FAILURE RESPONSE... AFTER 60 seconds the system will fallout to this block.
}];
// Create a queue object
NSOperationQueue *myQueue = [[NSOperationQueue alloc] init];
// Add the operation object to the queue
[myQueue addOperation:myOperation];
The following is the error I get print the myFailureError object
Error Domain=NSURLErrorDomain Code=-1001 "The request timed out." UserInfo=0x8481000 {NSErrorFailingURLStringKey=http://www.mylocalmachine.int/myfile.cfm, NSErrorFailingURLKey=http://www.mylocalmachine.int/myfile.cfm, NSLocalizedDescription=The request timed out., NSUnderlyingError=0x9189e20 "The request timed out."}
Update----
I believe I have narrowed the issue down to what I beleive to be an issue with the iPhone simulator accessing IIS 7. It will access previous versions of IIS on the same network using the same code no problem.
The problem may be in the iPhone Simulator's User-Agent. I have tried to find a way to change the iPhone Simulator's User-Agent or allow the User-Agent in IIS 7 but can not seem to figure it out. The User-Agent the iPhone Simulator 6 is presenting is (iPhone Simulator; ios 6.0; Scale/2.00).
Does anyone know how to either allow this User-Agent on IIS 7 or change the User-Agent in the iPhone simulator?
Has anyone else seen this issue?
Thanks in advance,
Ed
Update----
Hi Everyone
Ok so I figured out how to change the User-Agent and Content-Type using the NSMutableURLRequest. I changed these to match what the browser would send, FireFox browser, and tried again to no avail. I still believe there is an issue with the configuration of IIS 7.5 but I can not find it...
Thanks for anyones help!!!
Ed
please try to remove last 2 lines of code and write
remove this
NSOperationQueue *myQueue = [[NSOperationQueue alloc] init];
[myQueue addOperation:myOperation];
add this instead
[myoperation start];
and also write failure:nil before that ending square bracket(]) like
AFJSONRequestOperation *myOperation = [AFJSONRequestOperation JSONRequestOperationWithRequest:myRequest
success:^(NSURLRequest *mySuccessRequest, NSHTTPURLResponse *mySuccessResponse, id mySuccessJSON)
{
// PROCESS THE SUCCESS RESPONSE;
}
failure:^(NSURLRequest *myFailureRequest, NSHTTPURLResponse *myFailureResponse, NSError *myFaliureError, id myFailureJSON)
{
// PROCESS THE FAILURE RESPONSE... AFTER 60 seconds the system will fallout to this block.
}failure:nil];
let me know is it working or not...!!!!
Happy Coding!!!!!!
I have resolved this issue. I will post what the resolution was to hopefully help someone else with a similar issue.
Turns out the problem was AVG installed on the system that was running IIS 7. It was a difficult issue to determine because any other system could access the web server with out any problems. It was only specific with the iPhone simulator accessing the system running IIS7. Even Safari or FireFox running on the same Mac would work just fine. Now what within AVG was causing the problem... That is yet to be determined.
I truly hope this helps someone along the way!