After the last Postman update I'm getting the error in the title on the Collection Runner page. I have been running about the same number of collections as always, but I noticed an automatic update to Postman this morning (even though I have that setting turned off).
I've viewed the changelog page as mentioned in other posts, but there is nothing on there to get the previous version. This is very frustrating and costing time and therefore money.
Tried to find info to downgrade to previous version but was not able to. I downloaded and ran the installer from the website anyway, but when I try to open Postman now I get an error "Version mismatch detected. Looks like you've used a newer version of the Postman app on this system. Please download the latest app and try again."
I got an answer from Postman support. Looks like they have decided to reduce the usage of the free version, even offline, to 25 collections runs per month. You can get more for the paid version. Wonder if they asked their users how they feel about that before they imposed this upon them.
Email excerpt: "Collection Runs will be available with Free(including offline use) and Basic plans at 25 runs per month."
A work around is to use Newman, which is not restricted, at least for now.
Related
I have an app on the "Internal Testing" track with a couple of friends as registered testers. They could all install it, no issues here. But they don't get updates automatically when I publish a new version on this track. The only way to install new updates is to uninstall the app and install it again via the invite link.
First thing I learned about this is that Google will not enable auto updates on Internal Testing if they haven't done at least one review of the app (although the track itself doesn't get reviewed). So you have to submit one version on the "Closed Testing" track in order to get it reviewed. I did this and it got accepted but still no updates on "Internal Testing".
Since I got reviewed on "Closed Testing" I published several new versions on "Internal Testing" but none got pushed to my users. They don't even see the update if they actively search for updates in the Play Store app.
I didn't find much explicit information about what to expect from the "Internal Testing" track wrt. updates, but this post says that it should be deployed automatically if the user has set their device to auto-update apps:
If your users have their device set to auto update apps, it will just update to the newest release when the device recognizes a release is available. (source)
What am I doing wrong here?
If this is not possible with "Internal Testing": what would be the right method to give a limited number of test user access to the app with auto-updates enabled?
Thanks in advance!
Edit: I found one way to update the app: if I long-tap the App icon and tap the (i) icon (this might be Samsung specific), I end up in the Play Store listing which shows an update button. The auto-updates are enabled btw, so it should have been installed automatically.
What I found is that testers list should be exclusive for different testing tracks. In other words, a tester should not have the same Android device trying to access internal testing track releases and open / closed testing track releases.
Did not find any official documentation from PlayStore on this, but learnt it the hard way.
Maybe this post is still helpful for you: https://medium.com/#tukai.anirban/internal-testing-in-google-playstore-47de955062ad
i am unable to publish any apps on my Google Play Developer account is says
An unexpected error occurred. Please try again later. (8869003)
can anyone please help me to get out of this?
Had same issue today.
In my case I had to logout and login.
Then everything worked.
In used incognito window and worked. Clearing cookies, cache might also work
It happens due to conflict between chrome signed in account and google console signed in account, signing out from console and resigning in will solve the conflict. Solaza suggested the same solution
I ran into a similar Android Developer Console Issue today.
I was trying to promote a Closed Testing Track (Beta) to Production.
I always got the following error (with random error codes):
An unexpected error has occurred. Please try again. (Random-Error-Code)
The solution was to create the new release by hand in the Production Track, rather than promoting up the existing Closed Testing Track.
This happened to me as well. It could have been because I changed my account email on the same day. I got it working the next day.
Things to try:
Use a different computer.
You have to select at least one country from the list of countries to test.
Give it 24 hours for Google to refresh your email change, and try again.
If nothing works, contact Google Play Console Customer Support, they have a chat window.
I faced this issue when update my developer profile on google play developer account. There is a featured app selection at the end of the page. I selected an app that is not published yet, caused the problem.
I didn't select that app as featured and it worked.
in my case it's due to the network issues that my laptop by default will use our company's system proxy, I guess it'll go through some internal firewalls before reach the outside world, the latency caused the error, i switched to no proxy mode, then everything working fine
Where does OSX Server store integration bots? Or is it my local Xcode who stores them? Server screwed my setup again, but this time I'm no longer able to see my bots.
Just want to express my deep frustration with Xcode CI:
OSX Server (or whatever it's called) is one of a kind piece of software, giving me incredible headaches lately with its' laginness, bugginess and poor performance. I think over the past week I experienced all possible errors Server has to offer:
"internal error updating bot" (please try again later);
"error reading service configuration" (or similar wording) - requires Xcode reset; continue to occur randomly again and again with no reasons;
"Xcode version is not supported" - only reboot seems to convince server to use Xcode which was already used previously
Randomly, fail integrations because "device is not connected", given that I test desktop application for OSX...
Finally, after yet another episode of screwing my setup, I no longer can see my bots on the server - they vanished. well done Server.
The bots and integrations are stored on the server.
The directory should look something like /Users/<xcode_server_tester_user_name>/Library/Caches/XCSBuilder/Bots
(OSX-Server 5.3 (16S4123), XCode 8.3.2 (8E2002))
I hate to say this but I found restarting the machine is a good way to resolve frustration No. 1 and 2.
device is not connected error often happens right after OS, OSX-Server or XCode is upgraded.
Usually reselecting devices from the XCode UI works for me.
Although sometimes it may require repeating multiple times and waiting for a long time for the device list to load.
On your OSX Server machine, deleting the simulator and re-adding it via Xcode->Devices sometimes helps too.
Another way is to delete all simulators from the linked Xcode on OSX Server machine and only keep the ones you want to test your project on. Config the bot to use All iOS Devices and Simulators.
Even though Xcode Server now runs as a specific user, the configuration files are kept in /Library/Developer/XcodeServer. You can also hit the Xcode Server API to get information about your bots.
In a Couchbase db.
I don't know how to access the contents though.
Enter this in Safari on your server
http://localhost:10355/_utils/
I must have done over 100 installs of DNN (dnnsoftware.com) now, and I have never seen the "wizard" complete correctly. It always hangs at 28%. Upgrades usually hang at the 53% level.
This appears to be a user interface fault, because if I wait long enough - how long? - I can navigate to the site and all is working perfectly. If I don't wait long enough, some part of the installation process restarts and gives me a site without a superuser account.
The installation process does not appear to have been adequately tested. Anyone know how to get the "wizard" to complete correctly?
I haven't experienced this high of failure rate with the installation or upgrade.
In order to diagnose the problem, do an upgrade. Before applying the upgrade, set the AutoUpgrade key in the web.config to "false". Then initiate the upgrade by going to:
[baseurl]/install/install.aspx?mode=upgrade.
Instead of the simple progress bar, you will get a detailed report of the extensions and items being installed or upgraded.
Before installing, make sure your file permissions are set appropriately on the website folder and you follow all of the steps as per the installation guidelines.
Also, if it turns out the issue is timeouts during the install due to a slow server, try increasing the execution timeout in the web.config in the <httpRuntime> node. The default executionTimeout is "1200" which is 20 minutes. if your upgrade or installation is taking longer, increase the value.
I am learning how to use the GDK and a nice explorer shared their HelloWorld project with me (https://code.google.com/p/hello-world-google-glass/source/checkout)
Unfortunately when I try to run the code I get the error:
java.lang.NoSuchMethodError:
com.google.android.glass.timeline.TimelineManager.createLiveCard
I have been searching for solutions, but the closest I could find to my problem was addressed in this post: Google glass sample projects are crashing
As the accepted answer suggested, I went into the SDK manager and updated my whole API 15, including the GDK sneak peak. My GDK shows Revision 2. Still doesn't work.
Even weirder, all of the sample apps Google included work just fine. Any advice?
EDIT: The sample apps DO NOT WORK just fine, I just realized when I manually launch the apps instead of voice command, I am actually given 2 choices of each app. One works, one gives the exact same error as described above. I imagine the working one came from MyGlass and the other is the one I loaded.
EDIT #2 I looked on MyGlass and it turns out my Glass is running XE11 instead of 12. I can't find any instructions on how to update it to XE12. Ideas?
GDK incompatible changes were introduced in the change between XE11 and XE12, so this makes some sense.
It is a little odd that you're on XE11 still, however. There is no way to force the upgrade, but it should happen on its own when charging and on WiFi. You may want to do a reset (hold the power button down for 15 seconds - this is just a forced power off instead of sleep and won't delete anything) and see if that resolves anything or a hard reset (which will delete everything) from the settings menu. You may also want to contact a Glass Guide for further assistance in getting the upgrade.
To connect to secured Wifi, you can try Connectify (http:www.connectify.me) and turn your laptop into a Hotspot. First, connect the laptop to school wifi with authentication, then share the hotspot with your Glass. I assume that you know how to generate QR Code for Google Glass to connect to Wifi. The info is available on glass.google.com/myglass
Once it connects via Wifi, it should be able to upgrade. If Glass does not prompt you to upgrade to XE12 after connecting to Wifi, you can try Prisoner's suggestion to reset the Glass. BTW, thanks for trying my Hello World app. Good Luck!