I see this error in my logs and I don't know what it means:
PAC Fetch failed with error [NSURLErrorDomain:-1003]
2017-06-08 17:07:56.157874+0200 xxxxxx[27059:7093559] [] nw_proxy_resolver_create_parsed_array PAC evaluation error: NSURLErrorDomain: -1003
At the same time I have a problem with a collectionView in my app. Don't know if it's related to the error or not:
Sometimes, and only if the app is used in one remote office of our Company, both with the simulator and a real device, a collectionView that simply receives an images array and show them on the screen, just stops working.
It's not like it didn't just load the images, it seems like the entire collectionView doesn't show up.
I'm testing the same app with simulators and devices in another office (another city) and it NEVER happened to me. Other that that "PAC" error, I only see some auto layout constraint problems, but I see the same errors in my logs and it still works perfectly.
The persons that are testing the app on the remote location say that they have to remove and reinstall the app to make it work again.
Any clue?
Had a similar problem fixed it by this method. Hope this helps.
The simulator uses your computers network connection, so I recommend checking the System Preferences > Network > Advanced > Proxies > Automatic Proxy Configuration : You must disable Auto Proxy Discovery.
Related
I am facing a strange issue, appium just flashes white Screen and does not open the app and if i keep the app open manually in the emulator it works. This issue just happen all of sudden.
My Observations on this issue. ( Not aware how to resolve this )
it happens only for few apps like Telegram
in the appium logs i dont see appPackage and Activity ( even though i have set capabilities)
in the logs i see this msg "[UiAutomator2] Neither 'app' nor 'appPackage' was set. Starting UiAutomator2 without the target application
"
in the logs i see " [AndroidDriver] No app sent in, not parsing package/activity "
Solutions I tried:
updated the app
appPackage and Activity is correct
tried clearing the cache of the app / reinstalled it
tried in real device still no luck
Any help is much appreciated
Logs are too lengthy to attach here
its resolved, It was a silly mistake, i had given a different property and in the desired caps i used a different property name (basically the place where i am storing the appPackage and Activity name and where i am using it was different )
I tried to release the iOS app in the Apple App Store. But it failed the review.
The app connects to Azure SQL Server DB on startup. It is implemented in C# Xamarin.Forms.
Initially (build x.x.x.0), I posted the app with following errors reported by reviewer:
"Snix_Connect (provider: SNI_PN7, error: 35 - SNI_ERROR_35)"
or
"Snix_Connect (provider: SNI_PN7, error: 40 - SNI_ERROR_40)"
I search the issue and tried to reproduce it.
I concluded that this usually happened when there are some issues with the Internet connection. I was able to reproduce it in the following 2 cases:
Disconnect WiFi router from the Internet, but preserve switched on,
and the iPhone still connected to this router.
Playing with VPN on iPhone. And while VPN is in progress of connection, I also tried to log in at this moment. This is not a robust method of reproducing the issue, but sometimes I got the error message above.
After this, I published the build on TestFlight. This is to test exactly the same binary as I uploaded for review. One of the teammates tested it on his device as well, and it worked fine on both devices: mine and him.
For completeness of the information, the app also worked fine on Android devices.
To make the error message more user-friendly I did the following.
If exception contains the errors above (with SNI_PN7), I replaced it with the following before showing to the user “Wi-Fi may be switched on, but not connected to the Internet, or Internet connection misconfigured".
In the current build, I have added the button “View report details” near error message. If the user taps this button he gets a page with stack trace and button “Copy report to clipboard”.
I asked reviewed, I also attached the file with screenshots on how to tap the button, and how to scroll page with the report and copy text to the clipboard. If he gets an error then I want him to copy the error report and share it with me.
After posting this last version, the reviewer completely ignored my request to share error details, and just attached a screenshot with the error message:
“Several errors occur: * Can't connect to the database. This may occur when there are issues with an Internet connection, unstable Internet connection, misconfiguration of firewall, VPN or antivirus, or issues with DB server. Please check Internet connection and configuration, and try again. * Error on checking connection to the database * Wi-Fi may be switched on, but not connected to the Internet, or Internet connection misconfigured (Ul code: 2)”
The reviewer just responded to me:
“We discovered one or more bugs in your app when reviewed on iPad running iOS 12.4.1 on Wi-Fi.
Next Steps:
To resolve this issue, please run your app on a device to identify any issues, then revise and resubmit your app for review.
If we misunderstood the intended behavior of your app, please reply to this message in Resolution Center to provide information on how these features were intended to work.
For new apps, uninstall all previous versions of your app from a device, then install and follow the steps to reproduce the issue. For updates, install the new version as an update to the previous version, then follow the steps to reproduce the issue.”
Nothing useful for me.
Note, in previous builds reviewer several times repeated me, that login/password is incorrect. Then I wrote to him directly in review note:
“In case I provide you wrong login/password (/) to test application, you will get the following error message: «Login or/and password is incorrect», possibly with additional info, but the message is very clear about wrong login/password. All other error messages are not related to the wrong login/password.”
After this, I sent the appeal to the Apple:
“The reviewer does not provide enough info why he/she has issues to login to
I added functionality to build x.x.x.5 so that the reviewer can get technical info right from the app, and I asked about this info during the review. But the reviewer didn't provide any information. It looks like he/she completely ignored what I have asked about in the notes”
There is no response for appeal more than 3 working days.
Note, it was 5-th build I posted for review. Every time the reviewer responses about 1 day. He stops responding to my clarification in the resolution center. It looks like he behaves in a cat-and-mouse way, but not willing to publish the app.
I try to publish the app from September 16, I fixed, and clarify what I could suppose may be error cause on the Apple reviewer side. But no obvious progress, and I actually can't realize what I can do more...
Could somebody give me an idea about what I can do more? What can be wrong with the app? Why reviewer device could have issues to connect to Azure SQL Server?
I added details here that I consider essential. But if you need more info, let me know.
Thank you.
I decided to include ads to my app which is under development and is not yet released. I created two zones in AdColony Dashboard, both are active and in "Show Test Ads only" mode but I still get this message from both in log even though configuration succeeds.
I get this message every single time I run the application. What could be the reason behind this?
This sounds like a connection issue that is keeping our SDK from communicating with our network. This could be because the app is monopolizing the network connection or that the device itself is not connected or even that you are not connecting to a stable/strong connection. If checking your connection status does not reveal the issue, this is most likely a one-off issue that must be worked on through AdColony Support at support#adcolony.com. When contacting our support, please include a full console log showing all app activity fro when you initialize our SDK through an attempted video view.
So I'm trying to make an application using the DJI SDK. In order for my app to function properly, my iDevice needs to be hooked up to the remote controller of the drone via USB.
This means I can't also run the app via xcode and get console output.
Is there a way of saving console output when using an app on your phone? I am aware of the crash logs, but sadly they don't provide enough info to be useful to me.
This problem started when I got a runtime error only when the device was connected to the remote controller. Therefore there was no way of isolating the problem since I couldn't tell what went wrong.
Another solution would maybe be a 1 female to 2 male usb chord, but I haven't found one online yet and even if I did I don't know if that would work.
Is there a standard way of debugging when using hardware that needs to be connected to the device?
from Xcode, hit window on the tool bar at the top, then Devices. Select the device you want to read the log from. However, this is the log for the entire phone, and you have to be plugged into the mac... so you'll have to run your tests, unplug from the DJI, plug into the mac, go to devices, and scroll through the log until you find the output from your app, and you won't be able to see real time expected outcome.
It's not ideal, but that's the only way I know of to see the apart from building an entire console log into your app yourself.
I think I have a correct implementation but in the simulator the only delegate method that gets called is bannerView:didFailToReceiveAdWithError:. It would seem that I'm contacting the iAd server properly, but it is consistently returning The operation couldn’t be completed. Ad inventory unavailable or The operation couldn’t be completed. Application has iAd Network configuration error.
I'm using the 4.5 SDK against the iOS 6 simulator if that matters. I've checked over the code (which is hideously too long to post), and all seems correct -- that the delegate method is being called is a good sign -- but the latter error message makes me suspect this might be about the app not being registered with iTunes Connect.
Any help is appreciated.
I discovered after watching this for quite a while that Apple serves up a number of errors, sometimes sequentially and often on startup. That meant that a number of errors were being reported regarding configuration or network unavailability that were simply test errors to make sure my code handled the errors correctly. The biggest issue here is that it can take 90-120 seconds before a banner is served with no error!
So with all the scary messages, I was getting no "your code is working fine, I'm just complaining to tweak you" feedback. It would be great if Apple served a success fir the first couple of banners so you could quickly check if your layout was correct.
I've found that something in my wireless network configuration is causing these errors. When I switched to 3G I get the banner almost instantly. And when I switch back to wireless, I don't get the error (as frequently at least). Not a high enough priority to hunt down the problem in the network config - it's just nice to know my code is working.