Channel priority of max and high the same in Expo?

#1

Hi, I made a snack where I set one channel to high and another to max. However, when I run the project, they show up in my phone as max for both of them.

I expect channel a to be Urgent and channel b to be High. I read the docs and it said that the default settings can only be set when the channel is initially created. I verified that I had never run anything else on this device before, so I know that I specified the desired settings of Urgent ('max') and High ('high') when they were first created as is necessary. And I never changed them in the Android settings GUI.

If the Expo app unconditionally sets channel priority to Urgent, how can I test that my app will correctly set the priority to high instead of max when I publish a standalone app? Or am I somehow doing something wrong (i.e., is the behavior of priority: 'high' supposed to be the same as priority: 'max' for some reason I don’t know)?

Thanks for any help.

I’m using a OnePlus5 with latest OxygenOS. EDIT: This is a OnePlus5 running OxygenOS-5.1.5 (Android-8.1.0 Android Security Patch level 2018-08-01). Based on the OnePlus forums, I suspect that this might be an OxygenOS bug. Please help me confirm by letting me know if if the snack produces the behavior I see for you if you and include your phone model and software versions. Particularly, if other OnePlus5 users have the same issue and non-OnePlus5 users don’t have the issue, that’d be helpful to know.

EDIT: A friend with OxygenOS-5.1.11 on a OnePlus6 also repros this. We need input from someone with a different phone brand still :wink:

#2

This also reproduces on Galaxy S8 and Android Emulator.

Is the channel priority setting actually supposed to make a difference between high and max on Android? Is maybe Android setting it to Urgent (max) for both when I want to be non-instrusive to users and set to High (high) by default instead?

#3

Hey @binki,

Thanks for reporting this. I pinged internally about this and one of the developers who worked on Notif Channels will be investigating!

Cheers,

Adam

1 Like
#4

Hi @binki - this is just a weird quirk of the Android OS. While they provide constants for “high” and “max” priority (along with “low”, “min”, and “default”), they make no guarantees about UI behavior or labels that these map to. Expo simply maps these straight through to JS (I’ve just verified there are no mis-mappings there) so what you’re seeing is that the OS you’re running doesn’t differentiate between “high” and “max” priority in the UI. ¯\(ツ)

FWIW, the “Experience notifications” channel is actually created with default priority, so you could try creating your channel without the priority field if you want the “High” text in the UI on that particular device.

1 Like
#5

Thanks for the reply! This really helped me get past being stuck.

I thought that my only options were low, min, high, max, but apparently putting any other string or omitting it entirely gets IMPORTANCE_DEFAULT which happens to map to the right thing on my device. Looks like that is what I want.

I had been looking at both https://github.com/expo/expo/blob/master/android/expoview/src/main/java/host/exp/exponent/notifications/NotificationConstants.java and https://github.com/expo/expo/blob/master/android/expoview/src/main/java/host/exp/exponent/notifications/NotificationHelper.java too and I can see that the mappings look right. That’s why I thought maybe my device/OnePlus was at fault, but apparently that’s stock Android behavior and how it’s supposed to work. I wish the Android API was a bit less vague on this—I get that they’re trying to provide an abstraction and prevent the developer from thinking about the actual implementation on concrete devices, but in the end I actually need to punch through that abstraction because I care about the experience as an Android user myself :-/.

#6

Hi @binki - glad that helped! I wish the Android API were less vague too :confused: we could change our mapping to match the current UI text instead, but then if Android decides to change its UI in the future our mapping would no longer make any sense. (It may already be different depending on the device/manufacturer, since there are multiple different versions of the Android OS.) However, I’ll update the docs to be more clear about this.

1 Like
#7

@esamelson Keeping the API mapping as close to the Android API as possible is good. The less magical it is, the more it’s like we’re writing native code and it’s a lot less fragile.

Looking forward to the documentation updates. Would be helpful if there were screenshots and a description of what users on most 8+ phones can expect to see for each of the priority/importance levels.

If I could change anything about the API itself, would be to recognize the string value 'default' and saying that that is the value that will be used if the priority key is omitted. Then the progression of 'min', 'low', 'default', 'high', 'max' would be fully represented in the API in a less confusing way IMO. Also, it is true that the Android API seems to be calling this “importance” rather than “priority” now. Maybe you’re staying with priority for consistence within Expo itself. Anyway, it’s too late for you to change the API at this point, so I just have to use it as it is now ;-).

closed #8

This topic was automatically closed 15 days after the last reply. New replies are no longer allowed.