Some Android devices being registered target platform Apple

Avatar

Avatar
Validate 1
Level 1
JAElliott
Level 1

Like

1 like

Total Posts

23 posts

Correct reply

1 solution
Top badges earned
Validate 1
Boost 1
Affirm 1
View profile

Avatar
Validate 1
Level 1
JAElliott
Level 1

Like

1 like

Total Posts

23 posts

Correct reply

1 solution
Top badges earned
Validate 1
Boost 1
Affirm 1
View profile
JAElliott
Level 1

12-01-2021

I'm working with multiple app dev teams and some of them are reporting that some Android devices being registered target platform Apple.

 

I believe this is something code related because my application registers fine on the same Launch property, but I wondered if anyone with technical knowledge of this process might be able to explain what might be the issue here.

 

See top line below...

 

image.png

Accepted Solutions (0)

Answers (2)

Answers (2)

Avatar

Avatar
Boost 5
Employee
Ryan_Morales
Employee

Likes

7 likes

Total Posts

24 posts

Correct reply

8 solutions
Top badges earned
Boost 5
Boost 3
Boost 1
Affirm 5
Affirm 3
View profile

Avatar
Boost 5
Employee
Ryan_Morales
Employee

Likes

7 likes

Total Posts

24 posts

Correct reply

8 solutions
Top badges earned
Boost 5
Boost 3
Boost 1
Affirm 5
Affirm 3
View profile
Ryan_Morales
Employee

12-01-2021

Hi @JAElliott ,

The target platform that a device has on ACS is determined by the ACP SDK which is running on the device (Android or iOS). I remember in a previous post you had mentioned that collectPii had been used to register devices on ACS. Has the Launch rule using collectPii to register devices been disabled? One possible cause for this issue is that you may have some Android devices which are incorrectly triggering the collectPii rule setup for registering iOS devices.

 

Additionally, it would be very helpful if you could provide some debug logs from devices that are showing the issue.

 

Thanks,

Ryan

Avatar

Avatar
Validate 1
Level 1
JAElliott
Level 1

Like

1 like

Total Posts

23 posts

Correct reply

1 solution
Top badges earned
Validate 1
Boost 1
Affirm 1
View profile

Avatar
Validate 1
Level 1
JAElliott
Level 1

Like

1 like

Total Posts

23 posts

Correct reply

1 solution
Top badges earned
Validate 1
Boost 1
Affirm 1
View profile
JAElliott
Level 1

13-01-2021

It turned out there were 2 issues causing this same end result. 1 was front end (dev), 1 seems to be an Adobe back end issue.

 

1 - Front end

Developer forgot to put the lifecycle start code into their app...

@Override
public void onResume() {
super.onResume();
MobileCore.setApplication(getApplication());
MobileCore.lifecycleStart(null);
}

@Override
public void onPause() {
super.onPause();
MobileCore.lifecyclePause();
}

When lifecycle start was included the device was registered correctly.

 

 

2 - Back end issue Privacy

Both developers of different Android apps discovered that if we configure Launch to default to privacy status UNKNOWN, then within the app when consent is given change it to OPT_IN, the devices get registered incorrectly.
If we default the privacy status to OPT_IN they get registered correctly.

 

I will need to raise this with Adobe support.