Develop Reference

Deeplinking Squareup pos app is not working

The documentation link: https://developer.squareup.com/docs/pos-api/build-mobile-web#step-5-test-your-code suggest straight forward code like this:
<a href="intent:#Intent;
action=com.squareup.pos.action.CHARGE;
package=com.squareup;
S.browser_fallback_url=https://my.website.com/index.html;
S.com.squareup.pos.WEB_CALLBACK_URI=https://my.website.com/index.html;
S.com.squareup.pos.CLIENT_ID=sq0ids-yourClientId;
S.com.squareup.pos.API_VERSION=v2.0;
i.com.squareup.pos.TOTAL_AMOUNT=100;
S.com.squareup.pos.CURRENCY_CODE=USD;
S.com.squareup.pos.TENDER_TYPES=com.squareup.pos.TENDER_CARD,com.squareup.pos.TENDER_CASH;
end">Start Transaction</a>
I tested it and it does not open any link, my devide already have app installed.
When I try this code:
Take a QR code 2
It open play store app with squareup pos app information, I need to directly open the app and not play store screen of the app, is there any way?

*UPDATE:
I got transactions to work after adding S.com.squareup.pos.LOCATION_ID={{ my_location_id }}. The location ID can be found in Square Developer Portal > Locations. Also if the POS app is passcode protected, you have to open and login with passcode before sending transaction.
*END UPDATE
I've been working through this same issue. I still haven't gotten a transaction to work, but have at least gotten the app to open.
Make sure the CLIENT ID is your production application ID. NOT sandbox.
The WEB_CALLBACK_URI needs to match the Web Callback URL defined in your Square Developer Portal > Point Of Sale API.
I hope this helps. If you do figure this out and get transactions to work, please post your solution for me and others who are sure to run into this issue since the documentation is lacking.

In web-based apps, how do I call a user's IMEI / UDID to the end of my web-based app's URL?

I'm making a pair of website-based apps for both Android and iOS interfaces, and I'm struggling with a part of it. Perhaps you guys could help me out!
I'm using Android Studio and Xcode, and launching the website through WebKit and WK WebView respectively. It's super simple, just an app which calls a website into it directly. No external navigation, nothing but a full-page website. And this part is working great!
But I do have one problem! I don't want my users to get consistently logged out if they close the app, or after a few hours of not using it. I'd like it to stay logged in for them, or to automatically log-in when they use it.
The maker of the website has given me a way to do this through the URL.
Basically, my URL currently is set up like "https://URL.com/x/y/z" and it goes to the website, and that is great, but I need to set it up to be "https://url.com/x/y/z/[insert user's IMEI or UDID here]". That unique ID from their Android device will keep them logged in. I've tested it using my own device with my own IMEI and it works great, but obviously using one specific identifier for everyone will not work. I just need it to call the specific user's IMEI or UDID into the URL, to complete it.
How should I go about this?

I am assuming that you are talking about an Android app that visualizes a website in an activity. On Android, you can retrieve the device's IMEI OR MEID string by calling:
android.telephony.TelephonyManager.getDeviceId().
But be warned, this requires that you add a permission to your manifest:
<uses-permission android:name="android.permission.READ_PHONE_STATE" />
You should inform your users why you are requesting this permission.

For iOS/Xcode, you can get the device UUID via UIDevice:
// Swift 4
let uuid = UIDevice.current.identifierForVendor!.uuidString
If you are targeting iOS 11 or newer, Apple introduced Device Check to get a device specific token. I personally haven't used it, but it sounds like it's use case is similar to what you're looking for.
Update:
From your comment, here is how'd you include it in the url string.
let urlString = "url.com/x/y/z/" + uuid

Change in twitter login

As we know, there have been changes in access to the twitter API referring to callbacks URLs.
So far, I have been using the identification callback with firebase, as I indicated here:
This has been working perfectly so far.
I read in the documentation that now you have to indicate the callback, according to android or iOS in the following way:
twitterkit- : // if using Twitter Kit for iOS or
twittersdk: // if using Twitter Kit for Android.
My application is only developed for android.
I have tried all the possible variants, but I always get the following error:
The client application failed validation: Not a valid callback URL format.
The tested options have been:
twittersdk://pfa89MGYola62VIln ........ (MY_CONSUMER_KEY)
twittersdk://MY_APP-android.firebaseapp.com/__/auth/handler
twittersdk://https://MY_APP-android.firebaseapp.com/__/auth/handler
I have activated and deactivated the check "enable callback locking" ...
I've tried everything, I'm a little desperate
For another test, I tried to register the URL callback as if it were the iOS platform
twitterkit-MY_CONSUMER_KEY://
and it was accepted on the first attempt.
I do not mind losing the relationship with firebase, the truth is that I was not using it, but I have a serious problem if I can not connect with twitter again.
I appreciate any help.

I found the solution, I put it here in case it can be of help to someone.
The truth is that it is not well specified in the documentation, you have to take two steps.
First: activate the "enable callback locking" checkbox
Second: indicate the android sdk for twitter, WITHOUT CONSUMER KEY, unlike iOS users.
It would be like this:
I hope it helps

I keep getting Validation Error: client_id provided in the request does not match any of the registered clients

This is driving me MAAAADDDD
I'm trying to implement "Log In With PayPal" on Android.
I'm using this sample app to try to get the login screen to show up. https://github.com/SeraphimSerapis/PayPal-Access-Android-Example
I have created an app on the https://devportal.x.com/ website as instructed, I just want to use OAuth 2.0, I did all the settings, no luck.
Also, followed the answer in here https://stackoverflow.com/a/16199165/546439 i.e. created a seller account on developers.paypal and clearly chosen login with paypal access and credentials etc, still no luck
I don't even know whether I should get the credentials from x.com or paypal.com, each of them give the same options but they return different keys, I am so lost.
Please help.
UPDATE: added auth URL I am sending
all of these are not working
https://identity.x.com/xidentity/resources/authorize?client_id=AXbPkxDchMYBBAWn2UExvLytvvbJDDXn6u-9nWNgF_J7SZmwQkdDTwxHkuKe&scope=https://identity.x.com/xidentity/resources/profile/me&redirect_uri=http%3A%2F%2Faccess.com%2Findex.php&response_type=code
https://identity.x.com/xidentity/resources/authorize?client_id=ATL6BhBqBYAwJnolhJDT04El5GtxxDzTMAQEb5kkCdZVDrMr_v5bWlPpw7nN&scope=https://identity.x.com/xidentity/resources/profile/me&redirect_uri=http%3A%2F%2Faccess.com%2Findex.php&response_type=code
https://identity.x.com/xidentity/resources/authorize?client_id=6956fcaf5d9fb4bbea22af7ce7f4cc7a&scope=https://identity.x.com/xidentity/resources/profile/me&redirect_uri=http%3A%2F%2Faccess.com%2Findex.php&response_type=code

This error meaning that you are sending wrong client_Id "or not sending it" within the URI asking for token which is sent to authorize URL /authorize?client_id={client_id}, please share your URI to check it.
client_id string Unique client identifier obtained through the
application registration process. Required.
from https://developer.paypal.com/webapps/developer/docs/api/

I stumpled across a similar problem. I already hat an REST app running and tried to implement PayPal Login. Everytime I tried to use the sandbox client_id I got the same error message as you.
Took me some time to figure out, that, in my own stupidity, I tried to call
https://www.paypal.com/webapps/auth/protocol/openidconnect/v1/authorize
instead of
https://www.sandbox.paypal.com/webapps/auth/protocol/openidconnect/v1/authorize
Now everything works for me

I had faced the same issue, I know this is a old issue and my solution may not be of much help. But I felt like sharing my fix.
I use devise for authentication and I wanted to implement PayPal login.
I configured omniauth for paypal inside config/initializers/devise.rb file. But by default the authentication path was "https://www.paypal.com/". As #Ello mentioned in his answer we need "https://www.sandbox.paypal.com/" url path for sandbox.
Then I figured out that we can change the url path to sandbox by passing sandbox as true in omniauth configuration.
So this is what I did in devise config file to resolve the issue
config.omniauth :paypal, PAYPAL_CLIENT_ID, PAYPAL_APP_SECRET, scope: PAYPAL_PERMISSIONS, sandbox: true

how do i like a message/notification with the linkedin api?

I have an application that authenticates users through the LinkedIn API. My questions:
is it possible for an application to like messages to all users who authorized it?
is it possible to get like list of a message to a subset of the application users?
I've been looking for a while, and can't find anything.

Via the Groups API of the LinkedIn APIs, you can like a post in a particular group using the following JavaScript code (XXXX is the particular post id):
IN.API.Raw('/posts/XXXX/relation-to-viewer/is-liked')
.method('PUT')
.body("true")
.result(function(result) {
alert(JSON.stringify(result));
})
.error(function(result) {
alert(JSON.stringify(result));
});
However, keep in mind that likes should not be automated but user initiated - only users who have authenticated your app should be liking posts, and only when they manually choose to do so. Writing a script that automatically likes all posts from any user that posts a message from your app is against the LinkedIn API terms of service.

Can't confirm for sure but maybe this link about likes can help u and give a clues about possible options.. Reported example you can find here or here. However I have no guaranty that this works cause I am not author of those posts.. Maybe u will find better and more accurate answer at LinkedIn API forum..
Hope it helped a bit.. Cheers