I'm setting up two BC applications and here's a scenario when I need to remove one of them from users store. Is there a way for app owner to initiate uninstall process?
In docs I saw only user-initiated uninstall
There isn't really a method for an app to be "force uninstalled" from the app creator's end apart from invalidating the token by essentially deleting the app. We can definitely take that as a feature request, though. If you're able to share any additional details about your scenario for needing to uninstall an app from your end, that would be helpful context for our team.
Related
We are working in RingCentral application and APIs with SMS and fax permissions.
The application recently moved to production from Sandbox environment.
We have now a requirement to add 2 additional permission ReadAccount, ReadContact in the app which was not added during sandbox testing.
How can we do that? I don't see any option to modify the app. Is there any way we can modify the existing app?
As per I know once your app is in production, you cannot change anything.
You need to ask devsupport#ringcentral.com for any help. Once they added the permission with your request (not sure if they do.. most probably they don't) you need to test again for that permission you acquired.
The official recommendation is to create a new app, add proper permissions and graduate it. So in that case you need to go through again.
As per the reference here
"You can clone the app, give it a new name or add a version to the new app name. Add the missing permissions and run test in the sandbox the same way as you did for the first app. Graduate your app and finally replace the client Id and secrete to use the new app. You can suspend the old app after that."
Similar question here: https://forums.developers.ringcentral.com/questions/1059/how-to-add-permissions-of-read-call-log-in-product.html
So I've been building a Shopify App.
Currently I've gotten to the point where I get the permanent access code.
My question lies with the flow of installation.
Currently the store owner would create an account on my website, then click a button to install our shopify app.
taken to shopify app install prompt -> clicks install -> redirects to my site where I exchange code for access code.
This works fine. But where I am having trouble is what if once my app is on the Shopify Store.
A store installs it from shopify directly (meaning they don't have an existing account with me) I then have no account to save the data to.
How do I go about this?
I looked at other apps on the store. Some apps like Shippo can take you straight to their site first to create an account and then install their app.
What's the solution?
You misunderstand the install from Shopify. When someone installs from Shopify, they come knocking on your door. They introduce themselves as being ***.myshopify.com. Once they approve your App and accept your terms of service, you get to confirm their account, and hence you persist their data in your database exactly the same as someone that installed your App outside Shopify.
So when you say you no account to save the data to, well of course. They are a new install. So make a new record. Instead of an update, you to a create.
I am in the process of updating my Shopify App with new Permissions. This means there is a change in the authourize_url which would show up the permissions window when trying to install an app. I have also changed the redirect URL of the App. The App is currently listed in Shopify, and there are accounts using the App.
How would this change affect the current App Installs?
How do I go about this without having any downtime or manually asking Customers to uninstall and reinstall the App again?
What is the best way to handle such scenario?
You change the scopes. Your customers will therefore all have unauthorized oAuth tokens. The next time they try and use the App with the new scopes, your App will create a new oAuth token for their access as Shopify will prompt them to accept your new scopes.
It seems like pain, but it is the only way to go.
I'd like to use branch smart banner because it can open app if it was installed. But i've understood how it work. I need install ios sdk in my app and use setIdentity?
Alex from Branch.io here: the smart banner actually doesn't require the SDK to be integrated. setIdentity is a completely separate method used for tracking individual users, and isn't used at all for the smart banner.
However, integrating the SDK is definitely the easiest way to get things working, because even without it you would still need to set up a Branch account, configure all your link routing rules in the Branch dashboard, and then enable Universal Links in your app (if it's iOS). Since that is 90% of the SDK set up process, you might as well do the whole thing so you can also take advantage of things like install attribution and analytics!
I have read through many questions here about launching my app on login. I have followed this awesome tutorial suggested many times. That tutorial does work. BUT...
The one side affect that comes from using a helper app and registering it using SMLoginItemSetEnabled is that my app does not show up inside the user's Login Items in System Preferences.
There are several apps in the App Store (such as PopClip and Dash) that do what I am trying to do. I just can't figure out how...
UPDATE: I found out from the Dash developer that Dash is actually not sandboxed. He also believes that PopClip is not either. This could explain things... https://alpha.app.net/kapeli/post/3975968
UPDATE #2: I just got confirmation from the PopClip dev that it indeed is not sandboxed as well. https://twitter.com/pilotmoon/status/313746294361427968
With the last 2 updates, I guess the answer is clear. As of today, there is no way to accomplish this with Sandboxed apps.
Hope it's not too late.
In Apple's "Daemons and Services Programming Guide":
Adding Login Items
There are two ways to add a login item: using the Service Management framework, and using a shared file list.
Login items installed using the Service Management framework are not visible in System Preferences and can only be removed by the application that installed them.
Login items installed using a shared file list are visible in System Preferences; users have direct control over them. If you use this API, your login item can be disabled by the user, so any other application that communicates with it it should have reasonable fallback behavior in case the login item is disabled.
In sandboxed environment, only Helper applications can be installed in login items. You need to create one, stored in the Contents/Library/LoginItems folder of the main application.
Then you can used SMLoginItemSetEnabled to set the helper as login item and ask the login item to start the main application.