Solved

Unity SDK:: IL2CPP build doesn't send events for standalone

  • 22 July 2021
  • 2 replies
  • 55 views

Hello! I found the next problem.

Mixpanel doesn't work with IL2CPP build on windows (steam application).

Events aren't visible in Live view for IL2CPP mode.

Mono build works fine, all events are visible.


Engine: Unity 2019.4.17f

 

Build options:

Scipting Backend: IL2CPP
Api Level: .Net 4.x
C++ Compiler Conf.: Release

icon

Best answer by katonik 22 July 2021, 14:12

View original

2 replies

Have found the reason in debug build:

WindowsPlayer(DESKTOP-B08KLI4) [Mixpanel] System.InvalidOperationException: End of file reached while trying to read queue item
  at mixpanel.queue.PersistentQueue.ReadEntriesFromFile (mixpanel.queue.PersistentQueueEntry firstEntry, System.Int64 currentBufferSize) [0x00000] in <00000000000000000000000000000000>:0 
  at mixpanel.queue.PersistentQueue.ReadAhead () [0x00000] in <00000000000000000000000000000000>:0 
  at mixpanel.queue.PersistentQueue.Dequeue () [0x00000] in <00000000000000000000000000000000>:0 
  at mixpanel.queue.PersistentQueueSession.Dequeue () [0x00000] in <00000000000000000000000000000000>:0 
  at mixpanel.Worker+<SendData>d__19.MoveNext () [0x00000] in <00000000000000000000000000000000>:0 
  at mixpanel.Worker.DispatchOperations () [0x00000] in <00000000000000000000000000000000>:0 
  at mixpanel.Worker.RunBackgroundThread () [0x00000] in <00000000000000000000000000000000>:0 
  at System.Threading.ThreadHelper.ThreadStart_Context (System.Object state) [0x00000] in <00000000000000000000000000000000>:0 
  at System.Threading.ExecutionContext.RunInternal (System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, System.Object state, System.Boolean preserveSyncCtx) [0x00000] in <00000000000000000000000000000000>:0 
  at System.Threading.ExecutionContext.Run (System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, System.Object state, System.Boolean preserveSyncCtx) [0x00000] in <00000000000000000000000000000000>:0 
  at System.Threading.ExecutionContext.Run (System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, System.Object state) [0x00000] in <00000000000000000000000000000000>:0 
  at System.Threading.ThreadHelper.ThreadStart () [0x00000] in <00000000000000000000000000000000>:0 

We found the same issue, and after speaking with them, it seems that they will be fixing this issue soon, around OCTOBER-2021.

Reply