I have a simple Fiori app that is running in the launchpad. Now I am trying to start this app as standalone Fiori app because I don't need user information. The users should be able to call the app without logging in.
I have found a description how to call the app as standalone configuring the URL in the right way:
Running an Application Standalone
I gave that a try and it does not work in my case. No matter how I configure the URL, it directs me always to the Fiori Launchpad login screen.
Do I have to configure something in my app project to enable standalone? Or do I need to build the entire app as standalone?
Related
I was trying out flutter web and I wanted to share what I built with my friend so I wanted to know how to make my flutter web app open and run in browser just like html file where you would just click the file and open it with chrome and the site loads up
You cant open a flutter web project directly.
This is because flutter build web, will produce a Single Page App or SPA that will not work unless it's hosted via a server.
The user will either have to run a local server in-order to view the pages and for that you can use python 3's http.serve command or the dart variant dhttpd, the option is you can use a hosting solution like firebase or netlify to host your application if a local server is not possible.
I try to upload sample app to Google App Engine with existing progect ID.
Here is GAE screenshot
gae screenshot
I'm using the same ID in the progect.
But when I try to upload it with plugin from Eclipse then I recive an error:
eclipse error
The whole error from a console:
------------ Deploying frontend ------------
Preparing to deploy:
Created staging directory at: 'C:\Users\User\AppData\Local\Temp\appcfg2693799039714166602.tmp'
Scanning for jsp files.
Scanning files on local disk.
Initiating update.
com.google.appengine.tools.admin.HttpIoException: Error posting to URL: https://appengine.google.com/api/appversion/create?app_id=app1-152711&version=1&
404 Not Found
This application does not exist (project_id=u'app1-152711'). To create an App Engine application in this project, run "gcloud beta app create" in your console.
Debugging information may be found in C:\Users\User\AppData\Local\Temp\appengine-deploy7186088524405894873.log
Why I can not upload it?
This is actually the new intended behavior. App Engine will not be enabled for new projects until you go through the app creation flow in the Cloud Console under 'App Engine' to enable the App Engine service, or alternatively run gcloud beta app create from the console.
I just encountered this myself. The project has to be created in the Cloud Console AND you need to go through the project setup in AppEngine. Something must be broken in the API that creates the AppEngine part of the process while uploading. So doing it through the web interface creates the project for you... and then uploading will essentially fill it in.
It never used to be this way, so maybe something changed.
I have the same problem. This is what I did to solve it.
Log in to your google cloud account.
Select your project from the blue header bar.
Click the menu button(the 3 bars) on the top left of blue header bar.
Select IAM - you should permission for App Engine Service account. If not, you have to set it up.
To do that:
Click the menu button (the 3 bars) again
Click the App Engine
If you have not set it up, you will be prompt to do a tutorial.
Cancel the tutorial.
Go back to IAM.
Now you should see that the App Engine Service account added to the permission
Go ahead to upload. Should work now.
Make sure you are logged in with the correct Gmail account. At the bottom right corner of Eclipse you will see which account you have authorized, or you will see "Sign in to Google" - click on it to authorize Eclipse.
i am building my first phonegap app and when i open the app i instantly redirecting (window.location) the user to my server where my web app is hosted. Is it possible to load the phonegap plugins from there? Because the "deviceready" event is not firing and i cannot call any plugin functions.
I can confirm that loading remotely does appear to allow access to native components (when scripts are properly loaded) and that cordova.jsdoes not appear to need to be loaded by the local index.html bootstrap.
Short answer: Yes
Some 'gotcha's'
You will have to supply correct cordova.js version for the platform browsing to your site.
you can look here for more info https://github.com/apache/cordova-js. This project hosts the core js elements, and builds the platform specific cordova.js lib
Any plugin api's your app wants to interact with must be pre-installed into the Native App
any plugin with native code will have to be added to the project and deployed to device bundled inside the app. There is no way to lazyload native code. The js portions of the plugin could be hosted on your server, however.
More information, some apps that do this
The PhoneGap Developer App uses a similar technique to what is describe above and what you want. The only difference is that it is meant as a dev tool, and the server is a local dev machine.
The Cordova App Harness also uses this technique of pre-bundling an app package with plugins, to be consumed by remotely hosted resources
You cannot, deviceready only functioning if the app run on mobile phone environment only. If web based or dekstop application, it won't trigger.
No , dont do that . loading remote website will not able to intract with your plugins . and the app will get rejected on istore too
I've got the FB Connect plugin working with my Phonegap project native apps, but now I'm wondering what the workflow is for making it work with the web-app version.
When I run the web-app version, I get the standard Phonegap FB Connect errors, the last one being 'FB variable does not exist. Check that you have included the Facebook JS SDK file.' - this makes sense, as my web app doesn't have those js files, as they get injected during the PG Build process.
So what is the typical way of moving forward at that point? Can I use that last error as a way of determining 'ok, this is the web-app version, not native', and then what do I do next? Should have the Facebook SDK installed on my web-app?
Cheers
The git repo has steps for including the plugin in web app
Web App
www/js/facebookConnectPlugin.js contains the JavaScript SDK and API file. The API matches as close as possible to the native APIs.
Setup Web App Example
Host the www folder on a server and configure your Facebook dashboard correctly to test the Web APIs. Most people use Parse for easy testing.
NOTE : Developers should call facebookConnectPlugin.browserInit() before login - Web App ONLY
https://github.com/phonegap/phonegap-facebook-plugin
I am testing an application I developed using the .NET Devkit 2.0. In My Developer Center I am trying to run the connection tests in the Testing Your App section of the page. The OAuth test works fine but when I try to test OpenID I am getting an error.
When I click the "Test subscribe to app from Intuit App Center (OpenID)" it brings me to the company connect page, then I select the company, then it brings me to a free trial page of my App.
When I click "authorize" I am getting a 404 Error.
The URL points to: https://myserver.com/Error.aspx?aspxerrorpath=/myapp/OpenIdHandler.aspx
Where myserver is the name of my development server and myapp is the name of my application.
I am able to run the application from Visual Studio without a hitch. It connects and runs as expected but when I try it in the dev center it doesn't work properly.
Are my application settings correct?
Should I be pointing to OpenIdHandler.aspx in this instance?
App settings in the dev center:
App URL: https://myserver/myapp/Default.aspx
Disconnect Landing URL: https://myserver/myapp/Disconnect.aspx
Manage Users URL: https://myserver/myapp/Default.aspx
OpenID URL: https://myserver/myapp/OpenIdHandler.aspx
This is my first run at publishing to the Intuit App Center so any suggestions would be a huge help. I'm not even sure if the settings in the dev center are the problem or not.
Thank you
My firewall was not set up properly so it was not allowing any traffic to hit the desired pages of the site. Seems very curious to me that I was able to go to the default page but no others. Any way, it works now.