We are facing following issue while integrating google map with phonegap windows build
An app can’t load remote web content in the local context.
The same code is working for Android and IOS platform,
We tried to use Iframe for this, not able to get through this, anybody has any information regarding this, how to solve this issue.
We followed following url to test it.
http://www.creepyed.com/2012/11/how-to-use-the-google-maps-api-on-windows-8/
The app is working fine when we run it from local machine as the target, When we deploy the same app in windows phone lumia it is not able to include google map api, it shows the "An app can't load remote web content in the local context"
Thanks
Mohsin
Related
I'm trying to determine if I can access any browser api for chrome OS that will allow me to identify the device that its running on when the application has been force-installed in kiosk mode as a PWA.
We're running into exactly the same issue right now. The correct path seems to be to create a PWA and to connect it to a (pre-installed) extension that has access to the enterprise.deviceAttributes:
See https://developers.chrome.com/apps/migration:
"If there is a capability that your Chrome App has that the regular web platform can't provide, it might be available as an extension API. In this case, you use a progressive web app together with an externally connectable extension your web app can send messages to."
enterprise.deviceAttributes are only accessible if the calling App/Site is pre-installed to the device and not loaded dynamically, so it cannot run in the PWA by design.
But with this tutorial, it seems possible:
https://developer.chrome.com/extensions/messaging#external-webpage
We're looking into that right now and will post our progess here.
I have (had) a hosted app in the Chrome Web Store, built using the following Developer documentation:
https://developers.google.com/chrome/apps/docs/developers_guide
After being in the Chrome Web Store for years, I recently received an email saying my app does not comply:
Your item did not comply with the following section of our policy:
Do not post an app where the primary functionality is to install or
launch another app, theme, or extension. For example, if your app’s
primary function is to launch a desktop app that the user has already
installed, that is not allowed. Another example is a packaged app that
just launches a website.
My question is: Did the rules change? A Hosted App IS an app that launches a website. Does anyone know what to change in a Hosted App to make it compliant again?
A Hosted App, a Chrome App (successor to Packaged App), and a Chrome Extension are three separate things, distinguished by how their manifest.json file is set up. What this email appears to be saying is that you're not allowed to have a Chrome App (which they call a packaged app) whose only purpose is to launch another app or a web site. They are saying nothing about Hosted Apps, which continue to be allowed, as far as I know. (I have one in the Chrome Web Store myself.)
Is your app truly a Hosted App? Or, is it a (legacy) packaged app or a Chrome App?
I know what is metro app (just did some research) my question is where metro app runs. By my understanding :
Detktop app: running on your local machine with .net framework, and present data to user, you can launch/close it.
Web app: Publishing on IIS server, running from server render html to client, user can send request and get result.
Now, Metro app: is it just distributed on windows store, user can download/install it and run from local as same as desktop? or run from store, render something to user like web? or maybe some new working styles, can user close it?
Metro Style App was a working name before Microsoft settled on Windows Store Apps.
Windows Store Apps just like desktop apps run on local machine, but are often architected in more modern ways where the app would often connect to web services or push notifications that run in a data center. The UI though usually runs on local machine even if it is written in html/js with winjs.
The biggest difference is distribution - web apps run on the server so you only need to navigate to them in your browser to run the latest version. Desktop apps need to be installed - either with xcopy-style install, Windows installer or perhaps the ClickOnce technology. Store apps are distributed through the store which makes them easier to install and update than desktop apps as well as monetize, but are sandboxed (have limited access to local machine resources) for security.
What I want
I want to allow in app SSO between the Live Connect SDK and a single Mobile Services instance that I'll use as the backend for 2 applications, WP8 & W8.1. I want to do this without affecting existing users of the WP8 app that is already in the Windows Phone Store. Both apps will use the Live SDK for OneDrive access.
Existing Situation
I have a Windows Phone 8 application that uses Azure Mobile Services and the Live Connect SDK and I have set up SSO by
Registering the app in the Live Connect Developer Center
Setting the redirect URL in the Developer Center to the Mobile Services URL (used in the Live Connect authentication token)
Copying the Client ID into my app and passing it to the Live Connect SDK methods when I log in
Retrieving the Live Connect authentication token after login and passing it to the Mobile services login
Issues
This is fine but now I want to start building a companion Windows 8.1 app that uses the same Mobile Services instance and SSO but I'm running into a difficulty as below:
The Live Connect Developer Center app associated with the Windows 8.1 app needs to have the Package SID and the only way I can find to do this is to use the 'associate my app with the Windows Store' tool within Visual Studio. This creates a new app in the Live Connect Developer Center with the Windows 8.1 Package SID. I can't find any way to add this Package SID to my existing Live Connect app (i.e. the one used for the WP8 app).
I believe I need to use a single, shared Live Connect Developer Center app, and associated Client ID, for both my WP8 and W8.1 apps as the authentication token from Live Connect (documentation here) seems to include the 'user identifier - uid' that is 'An identifier for the user, which is unique to the app'. To me this also implies that if I change the client ID (i.e. effectively a new app from Live Connect's point of view) then it will appear to mobile services as if a new user is signing in and all their old data will no longer be accessible to them.
I have researched other people doing SSO across both platforms and they seem to be using a single app in the Live Connect Developer Center but in all cases that I have seen so far they use the Windows 8.1 app, because this has the Package SID, and set it to 'Mobile or desktop client app'. I have started from the other direction with the phone app first and I can't find any information about this. I'm also trying to avoid testing this all out in a live app in case it does cause issues.
I have posted in both the Mobile Services and Live Connect forums about these issues but without a reply. (I can only provide 2 links, check my profile in the Mobile Services forum for my other post).
My Question
How can I add Azure Mobile Services SSO to my new Window 8.1 app without breaking my existing WP8 app?
Thanks.
It looks like this question may have already been covered here:
Live Connect Authentication Token for use on Azure Mobile Services (REST)
Hope that helps!
This question has been answered by Matthew Henderson in the Azure Mobile Services forum
The simplified version is you need to use one Live Connect app in the Developer Center (i.e. the same Client ID used by both the W8.1 & WP8 apps)
To do this you either need to either:
a) Start with the Windows 8.1 app which will register the SID with the Live Connect app (this is the documented and easiest path) and then re-use this Client ID in the Windows Phone 8 app
OR
b) If you already have a Windows Phone 8 app as I did then you can change the automatically created SID association in the Live Connect Developer Center to allow the Windows 8.1 app to use the existing Windows Phone 8 Client ID. This is a less well documented feature.
I am trying to develop a PhoneGap app for the iOS. Is it possible to implement a WebSocket server and client in the native part of the app (in Xcode) to create a way for two instances of the app in different devices in a local network to communicate? The end result of the app to be developed is something similar to the app Air Sketch.
Other suggestions are appreciated. :)