Can any one explain me the difference between AppManifets(to my understanding it is .net package info) and WMAppManifest(to my understanding information about the app) ?
Thanks.
AppManifest.xml describes the deployment of your app (libraries and such).
This page describes it better than I can.
What is AppManifest.xaml in Silverlight?
WMAppManifest.xaml describes the
Application UI
Change your display name, and icons here.
Capabilites
Change what permission you want to ask the user to allow your app to do.
Requirements
Set a specific settings that the phone must meet, like having a front camera.
Packaging
Set various settings for submitting to the App store.
Related
I'm trying to publish an app for Windows Phone 8.1 and 10 (Only Mobile),
I already published a lot of apps on the same account. This is the same of another already on the store with just a different icon (different customer, it's B to B) and name, but from the 16 of october the policy for the windows store changed and now my app is blocked with the following reason:
App Policies: 10.1 Inaccurate Representation
Your app and its associated metadata must accurately and clearly
reflect the source, functionality, and features of your app.
•All aspects of your app should accurately describe the functions,
features and any important limitations of your app, including required
or supported input devices. Your app may not use a name or icon
similar to that of other apps, and may not claim to be from a company,
government body, or other entity if you do not have permission to make
that representation.
•Your app must be fully functional and must provide appropriate
functionality for each targeted device family.
•Keywords may not exceed seven unique terms and should be relevant to
your app.
•Your app must have distinct and informative metadata and must provide
a valuable and quality user experience.
Locations: Metadata
Notes To Developer
The app's "pin to start", "app list", or "games hub" icon does not
accurately represent the app and/or is a default icon. The
"pin-to-start" tile submitted in the submission package, which is
different from the icon and tile images in the app metadata, must
uniquely represent the app so users can associate it with your app.
For information about icons and tiles in Windows apps, see
http://msdn.microsoft.com/en-us/library/windowsphone/develop/hh202948(v=vs.105).aspx.
I searched on the internet but I didn't find anything useful for this problem and I don't get what are those "pin to start", "app list", and"games hub" they are talking about in the Note to Developers.
Anyone knows the solution?
Thanks in advice
Based on your description, it seems that you haven’t set the title images for your app. So I would like to suggest you to delete all of icons in your project and open Package.appxmanifest in Visual Studio and select the Visual Assets. Please make sure to replace all default titles with the correct size image that represents your app. And then you could need to create your app package and resubmit your app again.
By the way, if your project is UWP, you could use UWP Title Generator tool to generate correct size title quickly.
Update:
As your project is Windows Phone Silverlight 8.1, firstly, please prepare the correct size title, and then right-click Assets--choose Add--Existing item, you can choose the correct size title to replace the default title.
Then right-click Package.appxmanifest, choose open with--XML(Text)Editor, then you could need to make sure that the path of title is correct.
Finally, you may need to rebuild the project in order for the tile titles to show up properly.
Hope it is helpful to you.
I built some widgets and uploaded on my local marketplace, is there a way to share that?
And better is it possible to share a Mashup (the widget composition) without giving the
possibility to wiring to the user?
I mean the user should use an application layout without change anything.
You can make public your workspaces/dashboards following the steps documented in the user guide. Only the owner of a workspace will be able to modify it. I think this is what are you searching for.
Another option is to create a packaged mashup using the "Upload to my resources" option in the editor view:
Take a look to the "Advanced" tab, where you can block widgets (make them unremovable), block connections (make wiring connections unremovable) and embed used widgets/operator (by default packaged mashups depends on the user having installed all the required widgets/operators. This way you can distribute the widgets and operators used by the mashup in the same package).
However, take into account that this method is meant for sharing mashup templates, the user will always be able to add additional widgets and create new connections in the wiring view.
Once packaged, mashups/dashboards (and widgets and operators) can be uploaded to a WStore server (e.g. to the Store portal provided on FIWARE Lab) for sharing them with other users. The steps for making this is also described in the WireCloud's user guide.
I have the problem, revisited.
I have set up a working Marketplace instance (v2.3) but am unable to integrate it with Wirecloud. The marketplace is correctly registered but all the requests i am making to this Marketplace are throwing 502 error, even though i am actually able to see some results when querying the Marketplace server through a browser.
Indicatively, i can issue a GET command at http://:8080/FiwareMarketplace/v1/registration/stores/ and get an answer, but Wirecloud's internal APIs return a 502 (Bad Gateway).
Any idea on what might have gone wrong?
PS: This happens for WC v0.6.5. When upgrading to a newer (Beta) version of WC, everything seems to be performing as expected, i.e. the marketplace is correctly inserted and the stores are correctly retrieved and processed.
I've implemented a (for now) simple Background Agent in my Windows Phone 8 app. In the background agent, a WebRequest is made to update a stock list stored in XML in the IsolatedStorage. In other parts of the app, during debugging, I can see the currently logged in user; however, when the BackgroundAgent launches, the CurrentUser is null. At this point, shouldn't the CurrentUser be cached in the application? It seems to be cached for one part of the app (the main app) but uncached/unacceptable in others (the background agent).The current user seems to never be set in my Background Agent. I'm willing to provide more information, but does anyone know if this is a bug, or an implementation error?
PROBLEM: CurrentUser always set to null in BackgroundAgent. Are the sessions different in the BackgroundAgent from the main project (which is why it is never set)? Any help is appreciated.
Background Agents and Foreground Apps have no direct way of communicating as there is no guarantee that both will be running at the same time and they are separate processes.
The OS does not provide an API for communication so the two prefered methods are...
Use a web service to sync to data from Foreground App to Background Agent
Use Isolated Storage to share data between the Foreground App and Background Agent
In regards to credentials - there are methods available to encrypt the data in .NET, but for future reference, PasswordVault is available if you target WP8.1 (SL or XAML).
I read the OAuth documentation on Box's website, and understood the steps to give resource access to application.
However, it looks like all resources (all folders and files) under box account will be exposed to authorized application. Is it possible to only give certain folders' access to application instead of all of them?
thank you very much.
We're in the process of building out additional scopes but currently the only one available is full account read/write.
Is there any way to authenticate the application to use the Google Drive API without a native browser in an embedded system?
I'm looking for a solution to the user accepts and put your password and username using the OAuth2.0 without browser interactions... Is it possible?
My applications is build in Java Code.
Thanks in advance.
I am presently trying to do just this and I don't think it is possible because:
To authenticate in embedded device you need to use this process:
https://developers.google.com/accounts/docs/OAuth2ForDevices
the problem with this, is that it only accept limited range of scopes like:
--https://www.googleapis.com/auth/userinfo.profile
which works OK
but when you try with scope like:
--https://www.googleapis.com/auth/drive.*
you get invalid_scope.
If you find a solution please let me know, I have the same problem my device is embedded, has no screen, and is not available with remote desktop of the like.
thanks for any feed back.
Use the OAuth 2 device flow which is designed for cases where a browser isn't available on the device. It allows the user to complete the login & authorization on a separate, more capable device (phone/tablet/laptop) where a browser is available.