We are trying to get the Square Terminal API running on a live terminal (i.e. in production) for the first time, having gone as far as we can on the Square API Sandbox.
When we pair the Square Terminal to our software using a Device Code, and then try to create a Terminal Checkout using the API, we're not getting any response on the Terminal, even though the API indicates the Checkout is pending.
We've tried everything we can think of.
Does anyone have any idea what we might be missing?
Problem solved.
I had to upgrade the software on the Square Terminal. It took 5 rounds of software updates to bring it up to date, but now it works exactly as expected.
Related
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.
I have installed Gnuplot on a new Windows laptop, with all of the Windows updates applied and I am finding that Gnuplot is working fine in interactive mode but when I pipe data to it the graphs plot but I can't interact with the graphs via the mouse becasue the window freezes and says "Not Responding".
Interestingly, I can continue to pipe data to Gnuplot and the graphs are all plotted correctly.
I've tried 5.2.8 and 5.4.1 and I do not have any problems with either, on my old laptop with all the same Windows updates.
I'm at a loss! and wondering if it is somehow related to Microsoft anti-virus, anti-malware etc. I've tried disabling all of these but makes no difference.
I'm hoping that someone here might be able to give me some suggestions to try.
Thanks very much, as always,
John
This is a known problem under Windows 10. As best as I can determine from the bug reports on the gnuplot issue tracker, the problem is specific to gnuplot 5.4 + Windows 10. One reporter suggests that reversion of commit 651af626 would fix the problem (at the cost of significant slowdown), but I have not seen confirmation of this by other testers. If you can build from source and confirm that fix it would be a great help.
See https://sourceforge.net/p/gnuplot/bugs/2412/
I've been trying for the lase week to use GitHub from NB from a Windows 10 machine. Very little success.
The problem is the first Push step (Next) seems to time out will trying to connect, giving a Fail to Connect error. If Next is clicked again it often seems to connect... no more "failed to connect" message. However, the Finish step fails with a "cannot open git receive pack" message. On rare occasion, both steps succeed.
I am aware that there have been reported Windows 10 page load load time issues from the beginning, so am suspicious. But I report this thinking I am probably not the only person with the problem. For now, NB GitHub is useless. Too bad.
Turns out I had a network issue. Recently page loads and other Internet operations have been slow, and finally stopped altogether. I rebooted my cable modem, presumably resulting in a new IP from my ISP (Spectrum). And now the Push is working
Try first the first push from a Git for Windows in a CMD session, possibly using a simplified PATH, for testing.
If that does work, check if NetBeans has the same issue (pushing to a GitHub repo) with an HTTPS and/or an SSH URL.
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!
It's a late Sunday night and I decided to mess around with Facebook applications. Turns out they now offer you easy integration with heroku which, of course, I decided to try out.
I patiently waited for the toolbelt to download, installed it and, as usual, nothing will run for me without bit of a struggle.
So I did what I could, googled the problem I'm having and realized that the problem is most likely caused by the fact that my user folder contains non-latin characters.
To make sure that this is the problem, I created another user account, installed heroku toolbelt on it and it works just fine.
Are there any suggestions on how to get this to run without me having to work on the test account?
Thank you for your time!
edit
Forgot to ask wether it's possible to change the folder heroku uses?
edit
Still haven't found anything that would help me fixing this, is there really no way how to fix this?
I've attached the screenshot of error
I've stumbled on this post while being in much the same position. Here goes a solution:
Edit ...\Heroku\lib\heroku\helpers.rb such that def home-directory is as follows:
def home_directory
running_on_windows? ? (ENV['HEROKU_HOME'] || ENV['USERPROFILE']).gsub("\\","/") : ENV['HOME']
end
Now if you set the HEROKU_HOME environment variable to anything the Heroku toolbelt will use that as home. (FWIW: As I have run into this with other tools as well, I set up a link with US-ASCII-only letters to my standard home directory under Users.)
I think what you should do is run the heroku login command from the Git Bash client rather than from the default Windows command line. I have been using the heroku-toolbelt on Windows 7 for about a year now and have not encountered any such problem whatsoever. I had found a way to enable latin characters in the Windows command line sometime ago writing a program in CLIPS, but I don't quite remember how the command goes right now, or what configurations I did. However, if you don't have the standalone Git client installed you can always grab it from: http://git-scm.com.