Slow response when logging multiple callsigns

When logging two or three callsigns separated by commas if find polo can take up to 10 seconds to make the log entries, especially on my older iPad Pro. I do have a large notes file full of around 9000 names and callsigns so I’m not sure if that is a problem. Just suggesting if the code could be looked at around this feature to see if this process could be improved.

Marty,
Can you confirm if you are using the “personal dictionary” or text replacement feature with these multiple callsign entries?
If I manually enter 4 callsigns and tap save, they are entered immediately.
I suspect that’s because as each one is typed, they are looked up and there is no more looking up to do when I save.
Can you try it without the text replacement feature on and tell us if it’s faster to save that way?
Alan

This is without the text replacement feature. Perhaps it is an IOS thing. I can do a screen recording for you.

OK - I’m on Android and my tablet is not the high end. It’s middle spec.
And my internet connection has been pretty good for these observations.
My Android phone is also fast. (it’s pretty high spec).
My version is 24.12.1 - Build 24.12.0 (2412002)

BTW, the names lookup file has 77,000+ names in it. So the lookup in my tests is with that file too.

I use PoLo on an iPhone 13 Pro and multiple callsigns (comma separated) save immediately. No delay.

Andrew VK1AD

I tried logging 3 random callsigns all on the same line with my iPad Pro (1st gen). QRZ lookup was turned on and the locally stored names file was on. It took 80 seconds after pressing the save button for the log entries to appear on screen. The first callsign vk3fff it logged just once and then the next two that followed got logged three times (as you see in the attached photo)

When I turned off QRZ lookup and just used the names file everything works well. Quite fast!

Another polo user, Wes VK4HWP, a few days ago reported that he also got duplicates with multiple call signs separated by comma’s. He has QRZ turned on and does not have a names file. Wes has an older Samsung tablet he was using and along with the duplicates he reported about a 6 second delay. He was also struggling to maintain 4G coverage for that activation.

Note that I do not have a paid subscription to QRZ nor does Wes.