Zima Client iOS v1.6.1 Release Notes

Announcements
1

Zima Client iOS v1.6.1 is now available.

This update focuses on improving connection stability, file display, and app compatibility, along with fixes for several issues affecting everyday use.

:sparkles: What’s New

:one: Manual connections now support domains and custom ports
In addition to IP addresses, you can now connect using a domain name and specify a custom port, giving you more flexibility across different network environments.

:two: More stable device reconnection and switching
We’ve improved the device reconnection and switching process. Connections should now recover more reliably when switching between Wi-Fi, mobile networks, or other network environments.

:three: Improved file list display
We’ve optimized file list refresh and display behavior, fixing some cases where files might not appear correctly or the list status could become inconsistent.

:four: Improved app list and icon display
Compatibility across different ZimaOS versions has been improved, addressing issues where app lists or icons could occasionally display incorrectly.

:five: More fixes and improvements
We also fixed issues related to long-press file previews, login, and several UI details to improve overall stability and usability.

image
image1920×2400 394 KB

Download Link

Download the latest Zima Client and ZimaOS from our website:

Download ZimaOS and Zima Client

Questions or Feedback?

:e_mail: feedback@zimaos.com
:speech_balloon: Contact @Zima-777Spider

As always, thank you for your feedback and support. Please continue sharing your suggestions and reporting any issues on the forum. We’re listening!

Sincerely,
IceWhale Team

3

I tested Zima Client iOS 1.6.1 with my ZimaOS 1.6.2 system.

I can already confirm two improvements:

  • Web Links are working correctly now.

  • The previous folder display issue is fixed; I no longer see duplicate folders.

However, the reverse proxy issue is still not resolved.

When I configure my reverse proxy domain, the Zima Client automatically adds port 80 again, even though I enter only the domain without a port.

My reverse proxy uses standard HTTPS on port 443, so the automatically added :80 causes the connection to fail.

I will continue testing the other changes, but at this point the reverse proxy handling still does not work correctly for my setup.

1 Like
4

Can I confirm one detail: when you tested the reverse proxy connection, did you enter domain.com or https://domain.com in Zima Client?

5

I found an important detail.

When I enter the reverse proxy address using https://domain.com, the connection now works. I had not tested this exact format carefully before.

However, I have now encountered another problem.

When I open a Docker application that has its own reverse proxy configured, the Zima Client does not open the actual Docker application’s Web UI.

Instead, it opens the ZimaOS interface again.

So the connection to the reverse proxy itself works, but when I select a Docker application, the client appears to open the ZimaOS Web UI instead of the application’s configured Web UI.

The Docker application works correctly when I open its reverse proxy URL directly in a normal browser.

Could you please check how the Zima Client determines the Web UI URL when opening an application through a reverse proxy?