I think I'm doing everything correctly to build my Qt app for UWP, complete with symbols. I have published this app for PC via the Microsoft Store.
However when I look at the Microsoft Partner Center > Windows & Xbox > My App > Analytics > Health page, I see crashes and hangs but I'm unable to get additional information.
In the final "Failures" panel, it shows "Failure name" as "Unknown". When I download the data, I only get the following:
Failure name Hits Percentage
"[object Object]" "3" "100%"
What do I need to do to ensure I get useful crash reports?
Related
I'm reporting a very strange problem.
I have an app developed in Flutter and I have correctly integrated the Firebase library for using the Dynamic Links service.
The problem is when short links are open on a mobile device, it shows a screen with the message "Save my place in the app. A link will be copied to continue to this page", and a button OPEN to continue.
Using your link debugging tool everything seems ok
When I develop directly in debugging mode the problem does not present itself.
When I install the app from TestFlight sometimes it works and sometimes it doesn't. It seems random.
the problem could be that the app is not yet available on the store ?
Problem summary
I'm attempting to establish a connection between HoloLens and an Android device, which worked sporadically in the beta-version of the MRTK.
However since moving to the MRTK RC1 (Also Refresh), I've encountered issues regarding the QR-scanning. When pressing connect, the two devices seemingly finds eachother, however when the wearer of the HoloLens1 looks directly into the QR-code, nothing happens. (the white dot and "Locating marker..." text is showing)
Background summary
1. The Setup:
Implemented working MRTK RC1 Refresh
Cloned Feature-SpectatorView separately, copying only the "MixedRealityToolkit.Extensions" folder to the MRTK project.
"Spectator View - HoloLens" prefab added to scene.
First pressing "HoloLens" in the PlatformSwitcher, building for HoloLens1, then switching to "Android" and exporting the project to Android Studio.
Building the .apk from Android Studio
(opencv binaries are downloaded and implemented since beta version, I haven't since changed them from when they worked the last time.)
2. The Proces:
On the HoloLens, I press the "Connect" button in which a white text appears saying "Locating Marker..."
The Android phone presses connect and it goes to "Waiting for User" then as soon as a HoloLens is connected, it switches immediately to a QR code that should be readible from said HoloLens.
Looking directly at the QR-code and nothing new happens, connection does not establish further.
I checked if something was not ticked in Player Settings/Capabilities, but I can't seem to find what the culprit would be. Did I forget something in this proces?
There are a few things that could be causing this issue.
If the Android device is showing a marker, this means the two devices have established a network connection and are communicating with one another. Typically, when I run spectator view I enable the following capabilities: "Internet (Client & Server), Internet (Client), Microphone, Pictures Library, Private Networks (Client & Server), Spatial Perception, Videos Library, Webcam" in the Package.appxmanifest in visual studio. Pressing "HoloLens" on spectator view's unity platform switcher should typically achieve enabling these capabilities, but sometimes the package.appxmanifest doesn't get updated correctly in the visual studio project with subsequent builds in Unity. You can fix this by deleting your visual studio directory and rebuilding the visual studio project in unity.
If these capabilities are checked in the package.appxmanifest, it may be that you rejected a capability request when first running the application. If you open Settings -> Privacy -> Camera on the HoloLens, you can check whether your deployed spectator view application has camera access granted. You should be able to enable the camera functionality here if it is disabled.
There have been changes to both MixedRealityToolkit and MixedRealityToolkit-Unity spectator view logic, so cloning these items at different points in time may cause functions to no longer resolve (We're hoping to consolidate this code into the same repo/commit history in the future to prevent this from continuing to happen). Typically, in the Unity logs there will be errors stating that a function was not found for SpectatorViewPlugin.dll if the dll functionality is not resolving correctly. It sounds like this is not the issue you are hitting if things worked previously. But if it does turn out the case, it may be that you need to rebuild the SpectatorViewPlugin.dll to match the feature/spectatorView code you are using.
If you recently copied the SpectatorViewPlugin.dll and its dependencies to a new unity project, it may be that they aren't getting registered as usable by the windows uwp unity player. Make sure these binaries are in a Plugins\WSA\x86 folder within your assets folder. Also check the *.dll.meta definitions in the unity inspector to ensure the dll's are declared as usable for the unity wsa player/x86 builds.
We want to transfer data from instant app to installed app using Cookie API. Cookie API needs to have a play services version 11.4.0 or more. It works on lollipop, marshmallow and Oreo devices but crashes on Nought devices only showing following exception.
java.lang.NullPointerException: Attempt to invoke interface method 'void android.app.job.IJobScheduler.cancel(int)' on a null object reference.
It crashes when we use GoogleAnalytics.getInstance(getContext()) to get the Google Analytics Instance. But it works on all platforms except Nought.
I believe this is the same as this issue.
If that's the case, then this should fix it.
This is normally fixed in Google Play services for Instant Apps version 2.3. However, when you provision your device with Android Studio, you no longer receive OTA updates. You can check that from the version number (Android Studio provisioned version contains "sdk").
Try uninstalling Google Play services for Instant Apps. Then turn off Instant Apps and turn it on again. It should restore the final version (2.6-release), which contains the fix.
Deploying from the IDE will overwrite it still though.
So once it's updated, you can also remove the forced provision from the Edit Configuration dialog.
This was my issue with Firebase Analytics and I got the same error. So try that out and let me know if it helps.
I am using Xcode 8 and trying to upload my watchKit app to Testflight but its failing all the time.so far i have tried these options,
tried uploading it from Application Loader 3.6 and get invalid swift support, invalid watchkit support,and invalid executable error.
tried from Xcode 8. The app validates succesfully but upon upload to store, it just gets stuck. when i refresh, i do get an upload sccessful message but nothing is visible on testflight.
how to upload my watch app on testflight? please help
Have you enabled the version of your app to test on the iTunes Connect website?
I hope I'm not stating the obvious here, but if you:
Select your app in the "My Apps" section
Select the "TestFlight" tab at the top
Select "Internal Testing" on the left hand menu
Click on the "Select version to test" link in the page
Uploading an archive with a new version number doesn't automatically add it to TestFlight, so you have to go through this procedure every time you change version number (or on the first upload).
Once it's added, you should see the app appear in the TestFlight app on your phone. When it also has a Apple Watch app, and you have a watch paired with your phone, TestFlight will also install the app to your watch.
Hope that helps!
I have installed Wakanda Studio 11 build 11.195328 (and server) on my Macbook Pro/OSX El Capitan.
When i open the "School management" solution and try to display the onGet event code for a calculated attribute, i get an error window showing a message like:
The model.TimeTable.rec_type.onGet was not found
Clicking on the "OK" button does not close the window and I need to "Force Quit" Wakanda Studio to reopen it.
I think this is a bug, but i also would like to know if existing solutions need to be "migrated" to be compatible with the newest version of Wakanda.
I tested with School Management Solution and got the same error message when clicking the "+" icon next to rec_type attribute of Timetable class in model designer. But, I was able to close the dialog by clicking "OK". It did not go into infinite-loop.
School Management was written in WAK7 and it is compatible with Wakanda 11.195328. Meaning you can still deploy and run it in Wakanda studio and serve. The model API and structure however, have become deprecated. A brief introduction of model API and syntax can be found here.
School management is still fully functional in Wakanda 11. The only thing you need to do is add three users named: 'administrator', 'teacher', 'student' in Directory since the old directory is not supported anymore.
If you would like to continue development on School Management or solutions created from earlier versions, they will need to be migrated.