We develop our first app and use Shopify gem. It works fine and all functionality (including installation flow) is working well.
We've sent the app for a review and received an answer with following comment from their QA:
After installing the app from the Shopify App store, the app is redirecting to the website where the app is hosted. When accessing the app from a shop's app dashboard, the app is redirecting to the embedded version. This occurs when an initial OAuth request redirect fails to escape the iframe. Please refer to our embedded app OAuth documentation (https://help.shopify.com/en/api/embedded-apps/embedded-app-sdk/oauth) for further information.
Has anybody faced with this problem?
Shopify QA doesn't answer our e-mails and we couldn't find any useful requirements or information on shopify forums.
Related
I've integrated plaid using react-native-plaid-link-sdk in my react-native ios project. For OAuth flow, as mentioned in the document, I've added the redirect uri for OAuth flow. It works fine, where I was successfully able to redirect and connect the User's bank account in the external browser. Once done, it redirects back to the application. But in the app it is not resumed from where it left off from the plaid view, instead the app restarts where the HANDOFF event in plaid is not invoked. So I'm unable to update the selected accounts and other details to the server.
I've followed the OAuth requirements given here https://github.com/plaid/react-native-plaid-link-sdk#oauth-requirements
react-native version is 0.68.0
plaid sdk version is 7.4.0
Please clarify if any other additional implementations should be done to handle OAuth flow in react native ios. Thanks.
Two suggestions:
First, make sure the appdelegate is correctly set up, if relevant to your application, as described in https://plaid.com/docs/link/oauth/#react-native-on-ios:
"The PlaidLink component handles Universal Links by default. For integrations that use PlaidLink.openLink, Universal Links will not be handled by default. The useDeepLinkRedirector hook must be invoked by the component that calls PlaidLink.openLink."
Second, upgrade to the latest version of the React Native SDK, which has improved handling of OAuth redirects.
If neither of these suggestions works, please go ahead and submit a ticket to Plaid Support.
(Credit for this answer goes to Nathan from Plaid Developer Support, I am just passing along his troubleshooting suggestions!)
I am starting to create my first app using PHP laravel and osiset.
I have created a partner account and created an app as well. I have integrated the library also. Done with app installation and authorization.
Now I am stuck for the next step. I don't understand how can I link my code and settings implemented on my app to Shopify frontend. How can I link the app database to Shopify website?
I save all the customized data in the app and how can I link that data with Shopify website?
I am able to make a standalone app with PHP but don't understand how its data can be linked to Shopify website. How my app database can be used in shopify website?
I am new here. Any help is very much appreciated.
Thanks
You have two main choices in 2022.
App Proxy
Theme App Extension
Also, Post-Purchase extensions, for checkout stuff, but I digress. You should have no trouble injecting your special content using #1 or #2.
Update: It appears Twitter has fixed this issue. Clicking the authorize button now works! Thank you all for the responses.
I have a UIWebView that opens and directs to Twitters Oauth/Authorize webpage. The user signs in with there Twitter details and authenticates the use of our application with there Twitter account. This process worked perfect before the release of Twitter 6.37 iOS application. What happens now is when the WebView detects https://twitter.com/oauth/authorize?oauth_token instead of staying in the WebView it opens the native Twitter application and dies. If you uninstall the Twitter application everything works as usually it staying within the WebView. How can I prevent this from happening? I want to stay within my UIWebView and not automatically open deep links. I have been reading about the new URL deep link changes in iOS 9, but not sure of how to stop them from my application to other native applications. Thanks for any help!
As a workaround, in twitter authentication screen we can use the Go button on iOS typing keypad instead of using the sign in button on web view until twitter fixes.
Please refer the attached screenshot link for clarity.
Screenshot for the workaround
I ran into this issue as well and figured out it was because my authorize endpoint was set to https://twitter.com/oauth/authorize?oauth_token="+oauthToken (I believe this was in the original documentation). If you add api as the subdomain: https://api.twitter.com/oauth/authorize?oauth_token="+oauthToken, it will no longer trigger the deep linking and load the twitter app.
My answer to this via a Xamarin question:
Unless Twitter removes/updates the apps section of "https://www.twitter.com/apple-app-site-association" to allow a bypass or a secondary oauth that is not in the apple-app-site-association file I do not see how you would do it. These files are signed and iOS handles them at an OS level.
I have not played around very much with the continueUserActivity delegate and the NSUserActivity object that is passed to apps launched from UNI links, but I do not see a way for the launched app (i.e. Twitter) to return control to the original app, and at that point the oauth call-chain would be broken anyway....
Unique. Unlike custom URL schemes, universal links can’t be claimed by other apps, because they use standard HTTP or HTTPS links to your website.
Secure. When users install your app, iOS checks a file that you’ve uploaded to your web server to make sure that your website allows your app to open URLs on its behalf. Only you can create and upload this file, so the association of your website with your app is secure.
Via: https://developer.apple.com/library/prerelease/ios/documentation/General/Conceptual/AppSearch/UniversalLinks.html
I would report as an issue (bug?) to Twitter's Dev forum: https://twittercommunity.com
Is there any way to test your app or plugin before submitting for approval?
Or is there any sandbox for BigCommerce to test the apps prior?
How were the developers of the apps that are presently in the BigCommerce store able to test during the development phase?
You can test your app in a free trial store.
You can do this by:
Setting up a developer account
Logging in to the Apps section
Adding a draft app
Logging in to any Bigcommerce store (preferably a trial store) where you are an admin
Go to Apps then My Drafts
Install your app & test away
See https://developer.bigcommerce.com for more info.
To test your app on local, use ngrok.io to create a https url that tunnels to your localhost
I am developing iphone application for a shopping cart, i have done all stuffs but now its turn for online payment, the web version support paypal standard and the client want to stick with paypal standard the user will be redirected and paypal site and log and complete order. Is this possible on iphone?
Some days before apple does not allow any third party payment gateway. But now apple allows it to use the third party payment gateway like Paypal. You can used paypal library which allows you to pay your payment of products which you purchased from the app. For doing all this, paypal provides the library for mobile application development. I had used it in my 3-4 apps & works fine for me.
may be this could help you
link
link
Download Mobile Express Checkout Library from library and add the same to your project.
Why not you using PayPal SDk for Mobile device ? I have integrated PayPal in my app through their MPL library and Modified some stuffs like App Key and price,Store name Receiver account details etc. And its working fine for me.
check this link which is Already answered.
Also you can have a look at Getting started Guide.
PayPal API : How to integrate it in my App? IOS5
https://developer.paypal.com/
You need to implement paypal on your web server first.
Then go to that link from UIWebview….