For reference, I am using Firefox on Windows and it works for me. Firefox on iOS does not work for me.
Edited to add:
Chrome does not work. I tried to use the Chrome debugger (which I have next to no knowledge of) and it looks like to me that Chrome is blocking a request because the request headers are missing something or not correct and the blocked request is causing the search to fail. Firefox is probably not as strict and lets the request go through. Based on past history this could be Chrome tightening up security to make everyone safer but LifeMiles is violating the (possibly new) standard which they used to get away with but no longer is allowed on Chrome.
Here is a snippet of the error I caught on Chrome:
A cross-origin resource sharing (CORS) request was blocked because of invalid or missing response headers of the request or the associated preflight request .
To fix this issue, ensure the response to the CORS request and/or the associated preflight request are not missing headers and use valid header values.
Note that if an opaque response is sufficient, the request's mode can be set to no-cors to fetch the resource with CORS disabled; that way CORS headers are not required but the response content is inaccessible (opaque).
Add some more:
Hmm, this might mean that using an older version of Chrome might work? You would have to block auto-updates though and I don't know if that is even possible on Chrome. Probably easiest just to use Firefox on Windows for now.