Struggling with adding Crashalytics to our build.
We've downloaded and added the Fabric UnityPackage, upgraded to the latest version, signed in to our Fabric account from within the Unity Interface, and dragged the GameObject from the final step of the 'Prepare Fabric' modal into our first scene. Finally, we've built the game to Android.
After this, playing the game in the editor is prompting "Couldn't find Crashlytics GameObject" warnings, even though FabricInit and CrashlyticsInit are in the scene. The message pops up twice when running the game -- There are two consecutive Unity Scenes that this startup scene leads to.
There doesn't seem to be any specific documentation on the website, and the Fabric website leads us to the download page, as opposed to the dashboard.
Mike from Fabric here. The goal of this warning was to let you and other developers know that they haven't dragged in the CrashlyticsInit game object within a game, but this is being flagged in other cases due to how we try and detect this.
We're working on a more graceful way to get this point across, but in the meantime, if you comment out line 65 of Fabric/Editor/CommonBuild/FabricCommonBuild.cs then this will go away.
I removed the [PostProcessScene(0)] in Fabric/Editor/CommonBuild/FabricCommonBuild.cs
Because I only initialize and put the Crashlytics GameObject in my first scene.
I don't need it to check every scene to confirm if there is an object or if it needs to be initialized.
But still not sure if it will have some side effect.
Related
[[[Here are some screenshots](https://i.stack.imgur.com/ogjjR.png)](https://i.stack.imgur.com/M9yll.png)](https://i.stack.imgur.com/I9MkE.png)
I tried going to Google play console ---> app consent---> Data types. But I didn't know what to change
I selected "No" for "Does your app collect any of the required data types?"
A stack overflow posts says that I should change this to "yes" but when I did I didn't know what to select. My app doesn't collect any information it doesn't have ads and is completely offline, it's a game.
Sometimes Unity bundles Unit Ads by default in your project event though you don't use it. I'm not sure if that's the case with your game, but you can look into Package Manager and see if you have Unity Ads installed and uninstall it (This happened to me). Also check if Unity Analytics is there and remove it if you don't use it.
After doing this, the rest of the work should be actually completing the data form accurately. Just tick the boxes that match what you think your game is doing data-wise.
I've been following this tutorial https://learn.microsoft.com/en-us/windows/mixed-reality/develop/unity/tutorials/mr-learning-sharing-02 to make a Hololens 2 app that can be used by 2 or more users, however, I haven't been able to make it work, because after finishing the tutorial and trying to run the app, I get this build error message:
DllNotFoundException: AzureSpatialAnchors
I'm not sure what i'm doing wrong, I tried googling this problem but I seem to get nowhere. pls keep in mind that i'm a new developer unu
I included an image to give a better idea of the problem, it seems to be the only error message D:
(I tought the problem may have been something to do with my spatial anchor resource on azure, but even after creating a new resource and pasting the new ids, it seems to still have the problem unu. also, i do have a hololens 2 visor, so i'm sure the problem doesn't have to do with the emulator while pressing play.)
i hope the image helps
Azure Spatial Anchors are not supported in Unity Player (per your image, you are running it in Player) nor Hololens Emulator. You need to build & deploy the app to a Hololens in order to test ASA.
I downloaded the new Jih build of the Project-Tango Unity Samples.
Setting up my new project, I made sure to set the minimum API level to 17 in the Player Settings.
Howevery, when I try to start any of the two Meshing Demo scenes the App instantly crashes.
This is what I got from logcat, but I can't make any sense of it.
How do I fix this? Allowing out of date API did not help.
There's a bug with Unity on Tango. Try turn off the dynamic batching in player settings
I'm making a turn-based game, using the Game Center Turn-Based Gaming functionality. I'm using the simulator and my iPhone to test notifications of turn events. The results are very inconsistent. About 75% of the time when I make a move on the simulator and pass the turn I don't get any notifications on my iPhone. It seems that this function doesn't get called:
handleTurnEventForMatch:didBecomeActive:
I set the GKEventHandlerDelegate in the code that authenticates the local user and it seems to be set correctly. The fact that I get notifications once in a while suggests that this isn't where the problem lies.
Does anyone have any idea what could be the problem here? Could this be a problem with the Sandbox Game Center Server? Do they limit the amount of notifications you can send in a short amount of time or something like that?
Edit: I just found some posts of people experiencing the same problem, but no solution. No very recent posts though. Any updates?
Edit2: I also find that after a move, when I open the GKTurnBasedMatchmakerViewController on the other device it still says that it's the turn of the other player. When I close and reopen it the information is correct. Also, when I open the game GKTurnBasedMatchmakerViewController when it's still showing incorrect information, it does gives me the correct match object with the updated information. Could this be related in any way?
I thought I would share my solution with you, in the hopes that it is the same problem you are experiencing. As you can see from my comment to your question, I was having the same issue as you. It turned out that my settings in iTunes Connect were the culprit, unbeknownst to me. What you should check for is that you still have Game Center enabled in BOTH places that iTunes Connect requires. First, after going into "Manage my Apps" in iTunes Connect, select your app and on the right menu, and click "Manage Game Center". Make sure this is currently enabled. I would even recommend disabling it, and re-enabling it again for good measure.
In addition (and this is what I was missing), you must enable it in one more place. Go back to the previous screen when you first select the app. The top right is where you can select Manage Game Center, but we are looking on the bottom in the "Versions" section. Click the View Details button for your app, and make sure the Game Center button is enabled near the bottom. Again, I would disable and re-enable it here as well. Give it about 10 minutes, clear all your open turns and matches from the Game Center app (this might be an optional step), and build & run again. Hopefully, you will receive turn notifications properly again.
I got the same problem. However when i tested it on multiple devices it was working fine... May be some problem with the simulator
I am writing a game for the Microsoft PixelSense written in Unity, communicating with the table through the SurfaceToTUIO Bridge and the unity3d-tuio Unity Plugin.
I am currently trying to get the game to play nicely with the Microsoft PixelSense launcher. I have been able to get my application to appear in the launcher by mimicking the Surface Bing Application - duplicating a link to an XML file in C:\ProgramData\Microsoft\Surface\v2.0\Programs and creating the corresponding XML in the proper format.
When I go into Surface Mode - either through a dedicated Surface User Account, or through the Surface Shell on the Administrator's Profile, the game appears correctly on the launcher bar with the custom icon I set in the XML. The game launches correctly from the bar, and I can play it without any errors for about two minutes.
At that point, the Launcher closes my game. With a little research, I learned that its the Application's Responsibility to dismiss the Launcher.
Being that this is part of the Microsoft PixelSense SDK and not accessible to Unity, I've tried various methods to get around this:
I tried running the game in Single Application Mode. It turns out there is a different timeout that still waits for the SignalApplicationLoadComplete call.
I tried using the CriticalProcessMonitoring Disable and ApplicationProcessMonitoring Disable keys in the Registry.
I tried setting the LoadingScreenTimeout and SingleAppLoadingScreenTimeout Registry Keys to 0 - below their valid threshold.
What I want is to provide my users with the smoothest experience getting into and out of the Unity game. Currently we have to launch our game from the Windows Desktop, which can frustrate users due to the fact that Windows can't differientiate between a finger touching the screen, and a palm hovering above the screen.
Does anyone have a workaround, an good understanding of how I could spoof a SignalApplicationLoadingCall from Unity, or a suggestion of something to try?
Thanks!
Update: I've found some more things that didn't work:
I found the Microsoft.Surface DLL at C:\Windows\Microsoft.NET\assembly\GAC_MSIL\Microsoft.Surface\v4.0_2.0.0.0__31bf3856ad364e35. I imported it into my Unity project, but recieved a System.TypeLoadException that appears to be that the DLL is compiled with .NET 4.0, which Unity does not currently support.
I have been unable to find any COM objects that would allow me to communicate with the launcher without needing the DLL.
I cannot use a XNA wrapper program, as System.Diagnostics.Process.Start doesn't work in Surface Mode according to this post.