Numbers Row - randomly disappears on an iPhone

Hi dev team

Release: December '24 24.12.1 - build 24.12.0 (2412003)

I am using PoLo on an iPhone 13 Pro, iOS 18.1.1

Using the iPhone screen capture video functionality, I have captured the moment when the Numbers row disappears from the iPhone screen.

I was attempting to record a SOTA chase QSO and when entering the summit reference (VK3/VE-126), after pressing the ‘1’ key the Numbers row disappears.

This forum doesn’t permit video uploads therefore I have saved the video in a shared dropbox folder. How do I get the video link to one of your developers?

Andrew VK1AD

Andrew, you can send me the dropbox link and I can post it to Discord
Alan

Andrew,
I will send this on but I notice you have the numbers row active in this setting


And you also have numbers in your iOS keyboard.
Can you turn the PoLo numbers off and see if that avoids this issue?

Thanks Alan

I have disabled the numbers row. I will experiment tomorrow.

Andrew VK1AD

Got the video. Thanks!

Today I’m about to go out on a 15-park rove, but I’ll try to work on this later tonight or Sunday.

I have installed the latest version 25.1.0 - Build 25.1.0 (2501002) on my iPhone 13 Pro IOS 18.2.1.

The numbers row continues to randomly disappear when entering number values in the SOTA reference, as demonstrated in the December video.

Andrew VK1AD

I’ll look into it.

This undocumented feature is still present in the latest February release.

Regards

Andrew VK1AD

Sigh, totally forgot about this.

Making a note to look into it soon.

This should be fixed in the March release.

The defect is still present in release 25.3.0. I can now trigger the defect by using the numbers row for entering the numeral character in the ‘Their Call’ callsign field.

Example: Enter ‘VK1RX’ in Their Call field

The number row immediately disappears on pressing the ‘1’ character on the numbers row.

Phone: iPhone 13 Pro, IOS: 18.3.1

For the time being I have disabled the Numbers Row functionality.

Andrew VK1AD

This is very strange. I cannot reproduce the problem on my development phone.

I’m going to see if I can find another iphone to test it there with the app from the app store.