Phone number not showing up in app configurations for eSIM devicesSolved

Participant
Discussion
3 weeks ago

Hi everyone,

We’re deploying a Managed Google Play private app through Hexnode with custom app configurations to prefill user data.

Here’s the funny part, our employees use corporate SIMs for calls and personal SIMs for data like SIM 1& 2, but when the app tries to fetch the phone number using %phonenumber%, it sometimes decides to go and pick up the personal SIM number instead. So instead of our official contact showing up, we’re getting someone’s weekend SIM number! Is there a way to make Hexnode pull the number from a specific SIM slot in the app configuration?

Would really appreciate some pointers before our “official” app starts calling the wrong number!

Replies (5)

Marked SolutionPending Review
Participant
2 weeks ago
Marked SolutionPending Review

Jumping in here, we’re running into something similar!

Most of our corporate phone’s use eSIM profiles (SIM2), and when we deploy app configurations, the phone number field just gives us the silent treatment like totally blank. What’s odd is that %phonenumber% works perfectly fine when sending broadcast messages. But the moment it’s used in an app configuration, poof the number vanishes like it’s on vacation. Any idea how we can get Hexnode to recognize the eSIM number instead? Our IT team is starting to think these devices have a mind of their own!

Marked SolutionPending Review
Hexnode Expert
2 weeks ago
Marked SolutionPending Review

Hey @leo_scott and @noah-blake,

Thank you for bringing this up! We’ve taken this issue up with our concerned team, and they’re already looking into aligning how %phonenumber% behaves in app configurations with how it works in broadcast messages.

We’ll keep you posted once the fix is rolled out. We really appreciate your patience while the team works on this!

Regards,
John Cooper
Hexnode UEM

Marked SolutionPending Review
Hexnode Expert
1 week ago
Marked SolutionPending Review

Hello again,

Good news! The fix has been released.

We’ve now added two new wildcards that let you choose which SIM slot to fetch the number from:

  • %phonenumber_sim1% → Fetches the phone number from SIM1
  • %phonenumber_sim2% → Fetches the phone number from SIM2

You can now use these wildcards wherever it’s necessary to fetch a phone number, not just in app configurations or broadcast messages. They are supported on both Android and iOS devices.

This ensures that your apps pull the correct phone number, no matter which SIM slot it’s in.

Please feel free to reach out if you face any further issues.

Cheers,
John Cooper
Hexnode UEM

Marked SolutionPending Review
Participant
1 week ago
Marked SolutionPending Review

Just tested the wildcards options and it works like a charm!

Our apps are now pulling the correct corporate SIM number across all devices. Thanks for the quick turnaround, Hexnode team!

Marked SolutionPending Review
Participant
1 week ago
Marked SolutionPending Review

Same here! %phonenumber_sim2% finally fixed the blank field issue on our eSIM devices. Appreciate how fast this was resolved big thanks to the Hexnode crew!

Save