does any experiencing pub.dev site error down in Nigeria,? and it's affecting my HTTP host availability.
have try sorting out the answer on various platforms, which proves to be abortive.
Had the same issues for days until i downloaded hotspot shield.
Related
I have done Android Things OTA remote update 4 times and it was successfully happened. But this time it is giving error which is
"You've reached the device limit. Some features will not be enabled"
I do not know why it is giving me this error. Due to this I am not able to do the remote update.
If anybody knows this or any idea, please share.
The issue has been raised at the Google's issue tracker. There was stated the following:
You can continue to use the Android Things Console for development purposes. Functionality like OTAs will continue to work.
The 100 device limit is noted in the Android Things terms of service (Section 1.1):
Subject to the Terms, Google grants you a limited, revocable, non-transferable, non-exclusive, right to (i) access and use the Android Things Console and (ii) install the Software on up to 100 devices per product owned or controlled by you for the sole purpose of internal development and testing of devices that have integrated the Software.
I would also recommend reviewing the latest information on the FAQ page to learn more about the Android Things platform status.
I have encountered an odd problem the second time submitting an update to the app store.
I am building an app using Ionic Framework with a Java backend. Right now we use Firebase for user login.
We had a tough time getting our app onto the store this June because our server did not support ipv6 originally. After setting this up we got through review. But now that we are trying to submit an update (with a new reviewer) they cannot log into our app over ipv6 from a fresh install.
After further testing, we realized that our firebase url does not appear to be reachable over ipv6 (although we still haven't replicated the app review's report - our test correctly displays an error message, but they said that the app freezes).
I find it hard to believe firebase is not ipv6 enabled, but the testing indicates that that is the case. (once logged in ipv6 works fine with our server, we think firebase's capability to auto-relogin users offline is why we mistakenly made it into the store in the first place). Has anyone experienced similar issues with your firebase app? What did you do to resolve it? Did you end up having to abandon firebase or does the problem lie elsewhere?
p.s. I've looked long and hard but couldn't find any documentation about fireabse's compatibility with ipv6 or lack thereof. If anyone has seen this kind of documentation, that would also be immensely helpful.
Unfortunately Apple seems to miss-attribute any bug related to networking with IPv6-compatibility problems (as long as they hit it during compatibility testing). Most of the time, they aren't actually related to Firebase IPv6 compatibility.
Firebase has been tested on IPv6 and is compatible. You should test your app in an IPv6 environment, and check the stack trace of any error you find. If you see that Firebase is causing to the error, file a ticket with support.
Well, you could make some networking shinanigans like using an IPv6 reverse proxy that connects into your firebase via IPv4 which would lead them to be able to log in using IPv6, even though Firebase doesn't support it.
I suggest looking NGINX for that if you'd like to implement it yourself or looking into Cloudflare if you'd like to get that as a service.
I am trying to build an iOS application where I'll show the user a list of available WiFi Access Points to the user. First of all, I know that trying to do this will get my Application auto-denied in the App Store and that's okay, I'm only doing this for research purposes.
While I was researching, I found this GitHub library but it only works for 4.x and 5.x. This topic was also discussed in this question on how to use the iphone-wireless library but the top answer's link is down. Another answer linked this GitHub repo with a sample project but it seems that it only scans for other devices connected to where your device is currently connected.
I also found iPhone-Wireless' Google Code page but there's no guide whatsoever on how to use it.
Has anyone done this before? Listing all the available WiFi Access Points? I am okay with using libraries that will make the App Store reject my application as I have to plans of distributing it.
I am new to phonegap and coding so I am unaware as to how to use PhoneGap. First of all what I did was connect my PhoneGap (desktop) app thing to my iPhone PhoneGap developers app. On my iPhone it just says downloading... there is nothing else happening. I then tried using an Android phone to see if it works but it just says
unable to download archive from the server.
unable to properly connect to the server.
I dont know what to do so any help will be appreciated.
This can be caused by many things.
I assume you followed the steps from http://app.phonegap.com/ site:
you have created a phonegap app (at least a sample one using 'phonegap create')
you have a server running (using phonegap desktop or 'phonegap serve' from command line)
There are some things you have to check in order to know what is wrong:
Both the devices must be in the same network to 'see' each other.
The firewall is turned off or allows communication on the port the server is running on (default is port 3000)
Check if your antivirus isn't blocking the same port.
If you still have no connection here is the survey/checklist you should go through. It helps you get closer to the center of the problem you have (points: 7-11).
If that does not help you can always fill an issue (and attach above-mentioned survey) but I strongly recommend reading documentation first
NOTE: We finally uploaded the app but we didn't really troubleshoot this issue so I would appreciate if someone could share some valuable insight or experience pertaining to this question.
I've also checked the following 2 similar questions but these didn't help:
Error uploading ios application to itunesconnect “failed to open ssh session (16)”
App Store submission/distribution error “failed to open ssh session”
So...
Firstly, I am on a company network and just a week back we published a fresh new app using Max OSX 10.9.3 (13D65) & Xcode v5.1.1 (5B1008).
This week, while trying to upload an update for this app via the same system, I ran into a few issues.
1st try*firewalled
2nd/3rd try*firewalled
So, I got our network admin to open up port number 44001 and tried again.
Although it did reduce the number of errors, it failed again.
Thought we'd try from another system but same error.
4th try*firewalled
NOTE: No changes in network or system
5th try*firewall bypassed
So, I got our network admin to look into it and eventually we ended up bypassing the company firewall just for this upload session but it failed again.
6th try*firewalled
Thought we'd try from another system again so I switched to a colleague's system that hadn't been involved in this app's development, note that it was not bypassing the firewall, and it uploaded successfully in it's 1st attempt, albeit with a few warnings.
System was a Mac OSX 10.9.3 that we later realized had an older version of Xcode (5.0) but anyways...
Would someone be kind enough to shed some light or hints for the following errors/warnings:
Error: Failed to open ssh session. (16) (NOTE: this appeared with/without firewall/restrictions)
Error: Could NOT set the remote path to the existing package
Error: Could not create/set the package's folder on Apple's webDAV
Warning: Creating a new Signiant Transfer Engine
After having the same issue I've been able to fix this issue.
To solve this issue you need to:
Go to page 6 "System and Network Requirements" from https://itunesconnect.apple.com/docs/UsingApplicationLoader.pdf
verify that all of the ports and IP addresses are accessible.
After opening all of the ports from the table, I'm now able to upload my apps.
Enjoy!
I had the same problem when using my company's network because we use a proxy and due to security reasons all the needed ports and IPs reported on the official documentation were blocked. After switching to an external network without proxies, I was able to upload my new app.