I would like to transfer the ownership of my Microsoft Edge extension. The party whom I would transfer the ownership will manage the updates and features of the extension, and I would no longer want to be associated with the extension.
Is there any way of transferring ownership?
According to Publish to the Microsoft Edge Add-ons website, extension is associated with developer account.
If you want to "transfer" the extension, you can only delete it from your developer account and re-publish the extension with that party's account.
Related
I am using MDM to configure Email accounts on the devices using
Mail/Exchange ActiveSync payload.
I was wondering if there is a way where I can also configure OneDrive and DropBox accounts using MDM or Apple Configurator.
I know we can install the Apps but is there a way where I can add a specific account too?
Each application has different capabilities for being provisioned as it's being sent down to the device, therefore, there's no easy answer to this
However, firstly, I'd start with https://appconfig.org which is an initiative to getting developers to use the same format for Managed App Config. This also allows MDM vendors to "read" the Managed app config capabilities of an app, saving you the hassle of having to look this information up on the web
You'll struggle with Microsoft apps beyond VERY basic capabilities. However, for DropBox, there's some information here: Dropbox EMM support
I was approached to build an iOS app for a company. What would be the best way to go about this when developing and managing the project?
Would I publish this under my developer profile?
Should they create their own developer profile and have them give me the credentials?
Should we get a developer account and be members of a team?
Yes!! Client needs to create their own Apple Developer Account for current and future applications.
They needs to have paid account to publish App on store. Meanwhile either they can add you as developer or share the original credentials with your so you can sign the application with development and distribution certificates for Notification and publish.
It's a one time JOB, but trust me best option for You and your Client as well.
Here is your start.
id go with option 2 .... definitely not 1 so that they 'own' the final outcome and also you want to keep your account free of external dependencies
There are three ways you can go about release an app for client:
Release the app on your account and have a written agreement between yourself and the client to forward profits from the app to the client.
Ask them to give your Apple ID access to their account so you can upload it to their account (they shouldn't really give you their credentials for security reasons.
Upload the app to your account and once its gone through the review process you can then transfer ownership of the app from your account to theirs. (Documentation here)
I have an app on store and all client are used it. Sometimes some client needs additional feature that isn't wanted by others so in that case I make AdHoc build for that particular client, but it is not proper solution.
I think on Enterprise solution but apple not allowed to distribute outside the organization in it and I have all users are clients.
If your app has a user login, download a user specific configfile directly after login and check in code for feature availability by looking into it. Large companies like Spotify and also startups do it this way to test new features without releasing them to all.
Keychain access groups and application groups are both segregated using the app's team id.
Named pasteboards are also sandboxed using the team id.
Kerberos SSO seems to work well, but opening the KDC to the internet is a security hazard so it can only really be used together with a VPN.
The Shared Web Credentials API works well between native apps, but has intrusive popups showing up every time you attempt to access or even just check for the existence of credentials.
libdispatch can send messages to arbitrary apps, but the payload is limited to 64 bits and the recipient app must be currently running.
No unique device identifier that could be used to derive a key for a cloud-based encrypted KVS can ever be shared between apps not on the same team id.
…is there any way to share credentials (or any data, for that matter) between applications signed with different team ids, on recent versions of iOS? Apple doesn't allow migrating IAP, Passbook, etc to new team ids and it's blocking my team from implementing SSO between apps with historical team ids (M&As, etc).
You can open the app with deeplink that will reopen the other app with the infos you want to pass along. That's good for login but can be cumbersome if you want to pass a lot of infos back and forth.
All that I have researched integrating Dropbox iOS SDK requires logging in to authenticate/authenticate a user.
But this is what I want to accomplish
Use only one user account. (Without authorization)
Create a random public folder(in same account) and upload files to that folder.
Get the folder link.
It's basically sending generated files from the app to an account.
How can I possibly do this?
The API was designed with the intention that each user would link their own Dropbox account, in order to interact with their own files. However, it is technically possible to connect to just one account. The SDKs don't offer explicit support for it and we don't recommend doing so, for various technical and security reasons.
For example, any user who extracts the access token from your app will be able to read every file in the Dropbox account, delete everything, replace it, etc.
However if you did want to go this route, instead of kicking off the authorization flow, you would manually use an existing access token for your app. (Just be careful not to revoke it, e.g. via https://www.dropbox.com/account/applications.)