iPhone not tracked

Hi.

I’ve setup everything for my custom events in the dashboard and it is also being send by the client. Sadly I get only the custom events from the editor:

"platform": "editor-mac"

Sadly I don’t get any events from my iPhone device. There was no mention that I have to add something different for mobile, so any guess what I could be missing here?

Thanks for help.

We should be receiving and processing your custom events from the iPhone. However, these don’t show up automatically on the Integration page, so that may be confusing. A couple of things you can do:

  1. Wait a few (4-6) hours for our processing cycle to complete, and then check the Data Explorer. You should see your iPhone activity reflected when viewing custom events there.

  2. Run the iPhone version using Xcode and view the custom events on the Integration page. This should trigger the same “debug device” mode that you see when using the Unity editor, and your custom events should be visible on the Integration page.

2 Likes

Well, yes, it is confusing. And I’m not sure if it’s working correctly. I did 2) but I can’t see the platform “iPhone” or something like that in my events. Only the editor-mac.

Even more confusing is that I can see that the events are coming to the server, but they don’t show up in the data explorer. When I select there my custom event, then “no data” is shown with an exclamation mark.

Hmmm, 2) should work – we’ll investigate that. Also, if you submit a Support request at Unity Cloud we can take a closer look at your app and see what’s going on with the custom events.

Okay, I’ll do on monday mbirk. I’ll take the chance to double check my stuff at the weekend :slight_smile:

Ah, it’s a bug (scenario 2). We have the logic in place to check for running under Xcode, but it’s not passing the proper header to route the events to the Integration page. We will fix this and release a new version of the Unity Analytics plugin.

Ok thanks for the info mbirk.

I have the same problem, nothing is tracked from iOS devices. I waited one night and nothing shows up.

This is what I get when I enable logging :

{"header":{"appid":"4939963699315773233","userid":"298F0EB7-6E84-4D7C-979B-662237C88CA4","sessionid":7006606115158943447,"platform":"ios","sdk_ver":"1.6.2"},"events":[{"type":"appRunning","ts":1418150009200,"clicks":164,"duration":1087}]}
(Filename: /Users/builduser/buildslave/unity/build/artifacts/generated/common/runtime/UnityEngineDebug.gen.cpp Line: 56)

verb:Post
url:https://api.uca.cloud.unity3d.com/v1/events
accept-type:*/*
body:{"header":{"appid":"4939963699315773233","userid":"298F0EB7-6E84-4D7C-979B-662237C88CA4","sessionid":7006606115158943447,"platform":"ios","sdk_ver":"1.6.2"},"events":[{"type":"appRunning","ts":1418150009200,"clicks":164,"duration":1087}]}
customHeaders:
  key:dispatcher_state value:running

(Filename: /Users/builduser/buildslave/unity/build/artifacts/generated/common/runtime/UnityEngineDebug.gen.cpp Line: 56)

********************* RestResultCallback The operation couldn’t be completed. (NSURLErrorDomain error -1012.) m_NumbOfEventDispatched 1 m_NumbOfHighPriority 0 m_NetworkFailureRetryCount 0
(Filename: /Users/builduser/buildslave/unity/build/artifacts/generated/common/runtime/UnityEngineDebug.gen.cpp Line: 56)

{"header":{"appid":"4939963699315773233","userid":"298F0EB7-6E84-4D7C-979B-662237C88CA4","sessionid":7006606115158943447,"platform":"ios","sdk_ver":"1.6.2"},"events":[{"type":"appRunning","ts":1418150009200,"clicks":164,"duration":1087}]}
(Filename: /Users/builduser/buildslave/unity/build/artifacts/generated/common/runtime/UnityEngineDebug.gen.cpp Line: 56)

verb:Post
url:https://api.uca.cloud.unity3d.com/v1/events
accept-type:*/*
body:{"header":{"appid":"4939963699315773233","userid":"298F0EB7-6E84-4D7C-979B-662237C88CA4","sessionid":7006606115158943447,"platform":"ios","sdk_ver":"1.6.2"},"events":[{"type":"appRunning","ts":1418150009200,"clicks":164,"duration":1087}]}
customHeaders:
  key:dispatcher_state value:running

(Filename: /Users/builduser/buildslave/unity/build/artifacts/generated/common/runtime/UnityEngineDebug.gen.cpp Line: 56)

********************* RestResultCallback The operation couldn’t be completed. (NSURLErrorDomain error -1012.) m_NumbOfEventDispatched 1 m_NumbOfHighPriority 0 m_NetworkFailureRetryCount 1
(Filename: /Users/builduser/buildslave/unity/build/artifacts/generated/common/runtime/UnityEngineDebug.gen.cpp Line: 56)

{"header":{"appid":"4939963699315773233","userid":"298F0EB7-6E84-4D7C-979B-662237C88CA4","sessionid":7006606115158943447,"platform":"ios","sdk_ver":"1.6.2"},"events":[{"type":"appRunning","ts":1418150009200,"clicks":164,"duration":1087}]}
(Filename: /Users/builduser/buildslave/unity/build/artifacts/generated/common/runtime/UnityEngineDebug.gen.cpp Line: 56)

verb:Post
url:https://api.uca.cloud.unity3d.com/v1/events
accept-type:*/*
body:{"header":{"appid":"4939963699315773233","userid":"298F0EB7-6E84-4D7C-979B-662237C88CA4","sessionid":7006606115158943447,"platform":"ios","sdk_ver":"1.6.2"},"events":[{"type":"appRunning","ts":1418150009200,"clicks":164,"duration":1087}]}
customHeaders:
  key:dispatcher_state value:running

(Filename: /Users/builduser/buildslave/unity/build/artifacts/generated/common/runtime/UnityEngineDebug.gen.cpp Line: 56)

********************* RestResultCallback The operation couldn’t be completed. (NSURLErrorDomain error -1012.) m_NumbOfEventDispatched 1 m_NumbOfHighPriority 0 m_NetworkFailureRetryCount 2
(Filename: /Users/builduser/buildslave/unity/build/artifacts/generated/common/runtime/UnityEngineDebug.gen.cpp Line: 56)

The following line might be pointing to the issue:

********************* RestResultCallback The operation couldn’t be completed. (NSURLErrorDomain error -1012.) m_NumbOfEventDispatched 1 m_NumbOfHighPriority 0 m_NetworkFailureRetryCount 0

@mbirk Any news on the update?

Hi Pahe,
We’re working on releasing an update to the SDK with this fix. We’ll make sure to post here when it’s out.
Thanks for your patience.

@any_user - we’re looking into the issue your experiencing as well and will update you once we have a fix. Thanks for your cooperation!

@kentunity No problem and thanks for the info. We’re looking forward to the update. We’re in our final testing phase of the product and the analytics tool is 'cause on the check list :smile:

@any_user and @pahe - The new version of the SDK (1.7.2) fixes both of your problems :smile:

Thx! Already trying out! :slight_smile: