I'm developing and app for UWP using Microsoft Band. Eveything works fine, but when set to Release mode, I've got an error: Manifest references file 'Band.dll' which is not part of the payload.. In Debug everything is OK, app can be deployed to device and it's connecting to the my Band. In my Package.appxmanifest I have enabled bluetooth and proximity capabilities.
There is a fix available the link and install instructions are in this thread
https://social.msdn.microsoft.com/Forums/en-US/73f2d56d-9e8e-4b57-bcfa-0a972dfd75d7/update-11-generating-store-associated-package-fails-for-a-uwp-application-with-a-winrt-component?forum=Win10SDKToolsIssues
Related
Developer A created a Chrome extension in a Mac environment. Built, tested, published and working for all end consumers.
Developer B cloned the repo used to create the extension, built it in a Windows environment and the Chrome extension fails when posting data to an external API. The same is true when building the extension in a WSL2/Ubuntu environment.
Basic Troubleshooting
Verified developers are using identitical npm and node versions
Verified the zipped extension, built in a Mac environment, works when tested locally in a Windows environment
Odd Behavior of Extension Built in Windows
A popup created by the extension contains an error not present in the 'good' version.
popup.js:2 Uncaught SyntaxError: Invalid or unexpected token
And the offending line:
let payload = {}; // Object to hold data payload
Extension retrieves configuration data from a secure external API
Extension does not post data to a secure external API and does not report any API connectivity errors
Have any of you encountered this? If so, penny for your thoughts.
Update: VSC claimed the file was in UTF8 and, to be thorough, I re-saved the file as straight UTF8. The issue persists. (Thank you for the suggestion, wOxxOm)
We brought another developer into the mix and found the problem.
Turns out npm build isn't sufficient. Our process required npm run start in order to create a working deployable extension.
I will expand my answer if I invest the time into determining why this is.
Thanks again.
Is there a way to generate APK file for buildfire application that is under development so that QA's can test it?
I tried looking at the documentation but did not find anything related to it. Only option I saw was to publish app to Google Play Store.
You can test locally with BuildFire pluginTester. you can check: https://sdk.buildfire.com/docs/how-to-test-your-plugin-locally
For testing on real Android builds or iOS TestFlight builds, you can reach out to BuildFire for custom builds as long as you are on a non trial app and they will be able to provide you with these.
You can always preview your app on BuildFire previewer by following instructions when clicking the "Preview" button in the control panel as shown below. However, features that require special setup such as (Push Notifications, In App Purchase) or plugins that require special features to be added will not work.
This is a question that has been asked several times, but no solution has worked for me.
I finished coding a Xamarin Forms app and now, I want to release it. I signed the app with a new certificate and an Adhoc provisioning profile. Everything signs well.
But when I distribute the IPA, after installing the app, iOS shows this message:
"This app cannot be installed becaue its integrity could not be
verified"
I chosed Ad-hoc as provisioning profile config.
This app has the same namespace and bundle id as its preceding app found in the app store already. I built a new version, within a new solution and created certificates with the same bundle id.
The device on which I am trying to install it is an iPhone XR, that I use to test the live version of the app and the one in development. When I run the app in debug on the phone, nothing wrong happens. But signing and distributing causes the app to not run.
After several hours of debugging, I found out that my bundle display name for the new version of the app was written in lower case, whereas the bundle display name of the former app was camel case. When I changed the new app's bundle display name to camel case too, everything went smoothly.
This is so weird.
After getting out of a mode of procastinating, I've finally gotten to the item on the projects todo-list that says "Run on virtual device to see why it crashes".
My project is a libgdx application that I plan on porting to various platforms, the two most important ones being desktop and android.
During development I've exclusively used the desktop launcher, as it's a lot easier to fire up when just checking minor things.
I did build an .apk at one point just to see if it'd run out of the box, but it didn't. Now that I've tried via the virtual device, this is what the log says:
com.badlogic.gdx.utils.GdxRuntimeException: Couldn't load file: rifleman.png
The same goes for any other assets that my game uses. The files are all placed in projectname/android/assets, as I remember learning way back that this was the way to go.
The virtual device I tried with is the stock Nexus 5, but I tried running the .apk by uploading it to my actual phone with a crash right after start, and I assume the problem is the same and is therefore unrelated to the test-platform.
I am currently not using an assetmanager, as implementing this is scheduled for after getting the basic core mechanics up and running. In the mean time I'm loading them as such: new Pixmap(new FileHandle("rifleman.png"));
Using android-studio 2.2 on Linux Mint 17 Cinnamon.
Please comment if more info is needed.
Use Gdx.files.internal() instead of FileHandle().
From filehandle(string) method info
Creates a new absolute FileHandle for the file name. Use this for
tools on the desktop that don't need any of the backends.
Do not use this constructor in case you write something cross-platform.
I build Ionic app with node with express back-end , With this service i can fetch some json data using AngularJS http provider.
I can show the json data using browser.
But when i build my app and then install on my android device, nothing's shown.
This might be related to security. You may need to install cordova-plugin-whitelist and make the appropriate configurations - see https://cordova.apache.org/docs/en/latest/guide/appdev/whitelist/index.html
If this is not the case please provide more details about the error you see in the console