Built and deployed a simple list fiori app using Business Application Studio as a 'Managed Application Router'
New App is visible under HTML5 Apps in the BTP cockpit
In BTP launchpad, new app is visible in Content Explorer and can add it to managed content.
Can add new app to 'Everyone' Role
Create a new catalog, but new app is not visible when trying to add apps to the catalog. All other 'local' apps are and can be assigned to the catalog (or group)
Is there a configuration or setting that must be made e.g. when the app is deployed to BTP to make it possible to launch the managed router app from the central launchpad ?
If you're still facing this issue, make sure visualization parameters are configured for your app under Content Manager. This usually gets filled automatically when you add FLP configuration at the time of creating Fiori app from template in BAS (for example) and deploy to BTP. Only apps with visual representation are visible when you assign them to a group or a catalog.
Related
I would like to have multiple different iOS mobile apps inside one master iOS Mobile App.
Once the user login to the master app, they will have a list of the mobile apps, and each individual mobile app will be independently developed by different team and updated/deployed individually. There is only on master app that user will ever need to download to their device.
I know lot of big gaming companies are doing it, just not sure how they did it.
The apps you're talking about(like Roblox) doesn't have any real subapps. It only looks like this, but technically all those apps are just the app screens.
You can split your app code into modules, each representing an "app", and each team will only have access and work on it's own.
If you app will have a lot of resources, you can use On-Demand Resources. So it'll look like you're downloading an app. But you can only use this feature for things like images, videos, textures, but not the code itself - that's the main reason why you won't be able to deploy subapps separately. You'll have to deploy the master app when any of the apps is updated.
If all the sub apps were under 10MB you could use appClips to do this.
The "master" app can host a list of universal links to registered appClips.
This would then download each app as the user interacts with them in the master app.
The apple device will unload unused appClips over time, but with the master app won't be in danger of this as it would be a full App.
Users could then either open them from the master app permanently or open them through the App Library
Need to create MS Teams App creation trough script or an MS Teams API
Currently, we are creating the below steps manually through MS Teams site
Build a new App / configure BOT
Import existing App
Is there a way without accessing MS Teams App studio, can we create an App?
Your question's not really to clear, perhaps you can explain more. Basically though, App Studio helps with a few different things. In this case you're probably using it for the following:
1) Creating an app manifest - App Studio has a nice "wizard" to help create the manifest, but the manifest is just a zip file with some logo images and a JSON file inside - you can definitely create these without App Studio (but it's much nicer to do it inside App Studio - you can export it afterwards to get the zip file)
2) Installing your app - you -definitely- don't need App Studio for this. You can install your app in various ways. The most simple for a user, of course, is to be in the store, but even without that it's possible. The app needs to be "side-loaded", and you can do this in App Studio, or in the "Apps" list in Teams (right on the bottom of the left menu is an option to "upload a custom app") - for both of these, your organisation has to allow side loading of apps to Teams. If this is blocked, then you admin needs to side-load the app and make it available company-wide (or it can be restricted based on policies at https://admin.teams.microsoft.com/policies/app-setup/add)
Hope that helps
#MSTD Creating a Teams app can be done in 2 ways
Manually editing the manifest file in the solution, zip it and sideloading it into Teams.
Using App studio to create the app.
Currently, there is no API/Script to create the app package.
First and foremost, I am not the developer behind this application, however I am looking for a solution to this problem as I work at the company that runs the application and I've been tasked to do so. This is not a focused code-line question, but more so an application question.
Background: The application is an educational tool that simulates a physical science laboratory that is programmed using Flash. It is accessed from a Learning Management System (LMS) web browser - i.e. Blackboard, Canvas, etc. - through a link to the object. There are multiple simulated labs that are each their own object.
The main problem: The simulators/labs are able to be accessed on an Android device (phones & tablets) by prompting a download of a .apk file once the link is clicked on that device where they will have a menu that localizes all the simulators. This is to centralize all the simulators into one menu app. Now, when you attempt this process on an iOS device, it's obviously incompatible (.apk vs .ipa). We can create a runnable .ipa file for each individual simulator, but this is not efficient at all when attempting to execute on a mass scale (think district-wide access).
What I want to find out is the most efficient way to adapt the application for iOS since it utilizes Flash. The same process would be desired (click the link and it prompts a download of the menu app that holds the sims/labs).
Thanks in advance.
You need to enrol for apple developer program to distribute builds. Normal subscription consider distribution thought App Store, and it seems not your case. There is Enterprise subscription - it allows to create .ipa, that can be installed on any device, but distributed locally (Ad-Hoc). While assembling Ad-Hoc build in latest Xcode you can select opportunity to create distribution manifest as well (Xcode will provide description how to use it). Then you can upload manifest and iPad file to you file server, and share link to manifest with you user. Opening manifest on iDevice will launch installation of application.
I have a base project, which I would like to re-brand and resell for clients. So my question is: When I branch and create a new project obviously it needs to be a separate entity from the main. Is the only thing that separates these apps during submission the Bundle ID?
Since renaming projects can sometimes be a pain, what I'm doing is:
Creating the branch
Opening it in XCode and changing the Target name, and this changes the bundle ID because it's set to com.whatever.${PRODUCT_NAME:rfc1034identifier}.
So I'm wondering when submitting a new project, is the bundle ID the only thing that needs to be globally unique? or are there more attributes that I would need to change for each new branch/project?
Thanks
From my experience, only the bundle ID needs to be different.
A few things you should notice though:
You probably want the app splash screen / icon / icon label to be different between clients too
Under Build Settings your Code Signing Entity might need to be different too. If you have certificates+provisioning profiles which are specific to the bundle ID, you would have to create new sets of those for every client and use them when building
If you see that you're starting to change resources (like the icon / images for branding / string tables) between clients, using multiple projects and a shared static library may be easier for you. Take all of your shared code and convert it to a static library iOS project, and then create a separate project per client (normal iOS app project) which uses this library. This way all the metadata (like bundle ID, certificates, icons) can be different, and the code be the same.
If your app defines any URL schemes (for example, if you implement login with Facebook you need to do this), these schemes should be different between clients too. If they are the same, you are bound to have collisions when a user installs 2 apps on their device.
And one last tip regarding Apple policy:
If you are planning to submit all of these client apps under your developer account, this may be against Apple policy and your apps might be rejected. Apple wants you to open a dev account (and pay the $99/year) per client..
I want to build an iCloud based app that runs on both the Apple platforms, iOS and Mac. The app will use UIDocument on iOS and NSDocument on Mac to have a document based synchronization model - documents created on iOS will be available on Mac and vice versa.
The particular problem I'm facing is that I want the same iCloud container on both the apps. XCode creates a default container for the app based on the App ID, which has to be different on both the apps because this seems to be an Apple requirement - no two apps can have the same app id even if they are on different platforms.
So I left the default created container alone and added another container on both the Mac app as well as the iOS app. The app seems to work fine, I can create a new file package in both the apps in the correct place, but I'm having 2 issues:
The container does not appear properly in the iCloud settings management screen. In the entitlements section in XCode, I named the container as com.mycompany.myapp.mycontainer in both the apps. In the settings screen in iOS (Settings -> General -> Usage -> Manage Storage -> Show All) my app is listed as "mycontainer" instead of the App's actual name as I expected. Is it possible to supply a name and icon in the App's Info.plist to make it list properly?
My NSMetadataQuery is not working properly. I had made the iOS app with the Empty Application template, so the Info.plist was not properly setup with the CFBundleDocumentTypes key but I figured that out and fixed it. For firing my NSMetadataQuery in the iOS app, I'm using:
[self.queryCloud setPredicate:[NSPredicate predicateWithFormat:#"%K like '*.myextension*'",NSMetadataItemFSNameKey]];
with the search scope set like this:
[self.queryCloud setSearchScopes:[NSArray arrayWithObjects:NSMetadataQueryUbiquitousDocumentsScope, NSMetadataQueryUbiquitousDataScope, nil]];
I run the query after establishing the container's URL, I get the started and finished gathering notifications, but never the update notification from the NSMetadataQuery. Unless I go ahead and create a new document. If I create the document then I get notifications for Update, but only in that session. Next time I start up the app, the same settings don't give me any update notifications from NSMetadataQuery.
What am I doing wrong? Any pointers to articles on creating an iCloud document app targeting both Mac and iOS would be much appreciated! Suggestions, thoughts are most welcome.
I don't know about your NSMetadataQuery issues, but adding a shared iCloud container is easy, as long as you get the gotcha:
Pick one app ID that will be your shared cloud container. Doesn't matter if iOS or Mac OS X, you need to publish this app and it must be approved from the Apple Review Team* before your iCloud container will be available to any other app. e.g.
com.company.myawesomeapp
Note that you must not use a container name after your app ID (com.company.myawesomeapp.cloudcontainer), just use your appID!
Pick a second app ID (doesn't really matter), and create your second app. Open up Xcode and enable iCloud in the Capabilites Pane. Then under "iCloud Container Identifiers", add the identifier of your first (published and approved!) app
com.company.myawesomeapp
That's it!
There's just this one catch and that's the bottom line:
In order to use a container, an app must be available and approved. Before approval no other app may access your container, because technically it only exists as soon as your app is approved. Actually, it doesn't have to be available in the AppStore, it just needs to be approved (can be on developer held release).
You can only use a (shared) iCloud container if your app is published and has been approved.