I am currently working on an IOS app built through Swift on Xcode. Firebase packages are installed using Cocoapods, and all pods are updated. Additionally, I double-checked that the Plist and Google-Service Info files are correct.
This is the full error line I receive when logging into the app and trying to retrieve user information from the database:
nw_proxy_resolver_create_parsed_array [C3.1.1 proxy pac] Evaluation
error: NSURLErrorDomain: -1003
I am unable to figure out how to resolve this issue as there were no changes in my code and it was working beforehand perfectly.
I can provide code snippets if needed but since the app was working prior, I am assuming this isn't related to my code.
The only time I was able to solve this issue temporarily was to reset the package caches through XCode, allowing me to view posts and other content pulled from the firebase backend. Unfortunately, after I restarted the app, this solution did not work anymore, and the same error from above popped up. Since resetting the package caches worked initially, I am assuming there is no direct correlation between the error and my source code.
Does anyone have any idea as to ways I can solve this issue? It has prevented me from working on my app for several days now. Thanks for any help!
Update: After looking over my code one more time, I found that there was a missing dot in a line of code, leading to my IOS app not running. This did NOT solve the error of nw_proxy_resolver_create_parsed_array [C3.1.1 proxy pac] Evaluation error: NSURLErrorDomain: -1003, but since the app is working successfully, my problem is solved.
Related
Last time I used marmalade(https://kadena-io.github.io/marmalade/), I could see data on it. but I can't see them today.
I was investigating why I could not see any data, and found these api error.
Error Image
This means, server is not working? How can I fix this?
I'm trying to get my swift Mac app to launch at login using the method described in this page: https://theswiftdev.com/how-to-launch-a-macos-app-at-login/
However, I keep getting the following errors as soon as I call SMLoginItemSetEnabled:
Could not locate login item com.domain.LauncherApplication in the caller's bundle
Could not enable login item: com.domain.LauncherApplication: 3: No such process
I checked that the launcher app ID is correct multiple times, I tried changing it and changing its version number. I even tried cleaning the project and moving the base app to /Applications but I always get these error messages.
Any idea what the problem might be? (Notice the solution must not require me to disable App Sandboxing)
OK, I found the problem but it took a long time since it was so sneaky: In the Copy File Build Phase section I entered "Contents/Library/LoginItem" as the subpath instead of "Contents/Library/LoginItems" (notice the 's' in the end - can't believe I missed it). So thank you #vadian! You were absolutely right.
In my app I use Apple On Demand Resources.
I load the content with the following code:
currentRequest?.beginAccessingResources { (error: Error?) in
if let error = error {
onFailure(error as NSError)
return
}
onSuccess()
}
This works well with iOS 12 and Xcode 10, however with the latest iOS 13 and Xcode 11, I get the following error:
Begin: Request 0x0x283c498c0 response: Error: Error Domain=SZExtractorErrorDomain Code=4 "Hash mismatch for chunk containing offset 0: expected edf8721781dca63db1671ee3f0c7f199, got 621dea3aab25ce02a382f155971034c3" UserInfo={NSLocalizedDescription=Hash mismatch for chunk containing offset 0: expected edf8721781dca63db1671ee3f0c7f199, got 621dea3aab25ce02a382f155971034c3, SZExtractorActualHashValueErrorKey=621dea3aab25ce02a382f155971034c3, SZExtractorFileOffsetErrorKey=0, SZExtractorSourceFileLineErrorKey=470, SZExtractorFunctionNameErrorKey=-[StreamingUnzipState _checkHashForOffset:], SZExtractorHashChunkIndexErrorKey=0}`
I removed the assets, re-added them, tagged them, but the problem persists. What does this error mean?
I have encountered this error as well while developing an application on an iPhone 6s with iOS 13.1.2 using Xcode 11.0. On Demand Resources were working fine, but after changing non-related code, the completion handler of beginAccessingResourcesWithCompletionHandler: of NSBundleResourceRequest errored out with a hash mismatch error. I presume that the error means to tell that the request was not able to fetch the resources that were expected, at least according to the resource hash, which leads to the conclusion that the problem does not stem from the resources, but the expected hashes.
To clear the expected hashes, I have deleted my App from the development device and after rebuilding and deploying, on demand resources load again without error.
From our experience, the AppStore Review Team also encounters this error on their end from time to time. If you get a Rejection where the condition is caused by this error, tell them to remove the app from their device(s) before launching their tests again.
It might take a few attempts, but you'll eventually get a Reviewer that listens.
On-Demand Resource Management on iOS 13 appears to be wildly unreliable and prone to this hashing issue. The underlying issue is that the device is attempting to continue the download of a pending older version of the Asset Package and when attempting to merge the packets, it's encountering a hash that it is not expecting and breaking the file structure within the package.
This error means the asset hash in the internal database doesn't match the hash of the asset downloaded from Xcode. One way this can happen is if you install your app through the store or TestFlight, then reinstall it in Xcode. The easiest fix is to delete the app from your device. If your device is jailbroken, you can run the following command through SSH:
sqlite3 /private/var/containers/Data/System/*/Documents/Persistence/storeSystem.db "delete from odr_asset_pack where bundle_key like 'app.ish.iSH.%'"
My hosted app is showing a floating banner with a notice saying “Installation of this item may not work properly.” on its Google Chrome Web Store product page. The app is undiscoverable by searching the Web Store.
What is causing this problem? I find no additional information in the developer dashboard.
If you get this message, it is probable that there really is an error in the manifest or locale files (For example, in my case it was a trailing comma on the locale files).
The process y follow to solve the problem was:
Try to instal the app version you have just submited to the chrome store. When you try to install the app you will probably get a error message thats points you on the track of the problem of your manifest file.
Solved the problem on the app and upload it again. You may get the same error on the developers panel. Two thinghs can be appening:
A) If you've already corrected all errors in the manifest files remenber to publish the changes and what is more important remenber that the publication process may take a few minutes to become effective. The message will disappear after a while if everything is okay. (This explains why is you look on the internet for that problem you find people saying that the message will disappear after a while)
B) If error persist event after the publishing process have been complete finished. You may have not solved all error on the manifest file go back to Step 1
cheers
I had this exact problem. When I tried installing, I got an error message about a missing file.
When I removed my locales directory, everything worked fine.
I did two sample applications in ios.Both applications i have done using storyboard.Then after i did i copied the two classes of one application to another.Then i saved and compiled,it worked>But second time when i build the application and when i run that application,am getting error like this:
Couldn't register BundleIdentifier.application name with the bootstrap server.Error:unknown
error code.
This generally means that another instance of this process was already running or is hung in the debugger.(gdb)
How to resolve this error?Please give me some suggestions in resolving this issue.
The reason for this error is that you are testing app in either simulator or device and suddenly change for another without stopping it.
For this you need to properly close app from navigator before moving for another ios selection.
if encounter this problem then restart xcode and simultor(also reset simulator).