Zima Client iOS v1.6.0 Release Notes

[777-Spider]

This update brings a more reliable photo backup experience, full iPad support, improved video playback, encrypted folder access, and App Store management from your mobile device.

What’s New

Photo backup progress on the Lock Screen and Dynamic Island

You can now check photo backup progress from the Lock Screen and Dynamic Island without reopening the app. Background photo backups are also more reliable.

Full iPad support

File browsing, media previews, and photo backups have been optimized for larger screens, providing a smoother and more efficient experience on iPad.

Improved video playback

Support has been added for more video formats, along with improved playback stability and better recovery when errors occur.

Access encrypted folders from your mobile device

You can now enter your password directly in Zima Client to unlock and access encrypted folders.

Manage apps directly from Zima Client

After upgrading your server to ZimaOS 1.7.0, you can browse, download, install, and update apps directly from your mobile device.

Download Link

Download the latest Zima Client and ZimaOS from our website:

Download ZimaOS and Zima Client

Questions or Feedback?

feedback@zimaos.com
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

[isanto1306]

I updated the iOS client today and noticed that one of the major new features (app management) requires ZimaOS 1.7.0.

Unfortunately, I’m still running ZimaOS 1.6.2 because I encountered several issues with 1.7.0 and had to roll back.

From a user’s perspective, it feels disappointing to receive new client features that depend on a server version which is not yet stable enough for my environment.

I hope the remaining regressions in 1.7.x can be resolved soon, because I’d like to upgrade and use the new features with confidence.

[isanto1306]

iPad Layout issues in Zima Client 1.6.0

I found several layout problems on the iPad version of Zima Client 1.6.0.

• In the file browser, some folders are displayed twice in the content area.

• The left navigation panel overlaps the main content, leaving a large empty area at the bottom.

• In some situations, after opening a folder, the content view overlaps the folder list. I could no longer select folders on the left because the content view was covering the navigation panel.

These layout issues make file browsing difficult on the iPad.

Since full iPad support is one of the main new features in this release, I think these layout issues should be reviewed and fixed.

I really like that iPad support has been added. That’s why I wanted to report these issues, because I think the experience can become much better once these layout problems are resolved.

[isanto1306]

Additional feedback about the iOS Zima Client

I also found two major limitations that significantly reduce the usefulness of the mobile app for my setup.

1. Reverse proxy support

I access my ZimaOS through a reverse proxy.

While I can browse files, I cannot open any Docker applications from the Zima Client because it always tries to use the internal server address instead of my reverse proxy URL.

I think the mobile app should support reverse proxy configurations, just like the web interface. Many users access their NAS remotely through a reverse proxy.

2. Internet Links (Web Links)

Internet Links cannot be opened from the Zima Client either.

Since these links are part of the dashboard, I expected them to work from the mobile app as well.

At the moment, this makes the mobile app much less useful for me because I cannot access either my Docker applications or my Internet Links.

I noticed something that might help identify the problem.

The built-in IceWhale Community shortcut opens correctly from the Zima Client.

However, none of my own Internet Links (Web Links) work.

This suggests that the feature itself is working, but there seems to be a difference between the built-in links provided by ZimaOS and the custom Internet Links created by the user.

Maybe they are handled differently internally.

This information might help narrow down the cause of the issue.

I hope both features can be supported in a future update.

[isanto1306]

General touch experience on iPad (Safari)

I have another usability suggestion regarding touch interaction in Safari on the iPad.

With the previous CasaOS interface, I could use the system comfortably with touch controls.

In ZimaOS, however, the interface often behaves as if I were using a mouse instead of a touchscreen.

For example, when I try to scroll across the desktop, the system frequently interprets my touch as the start of dragging an app icon instead of simply scrolling.

I think the touch interaction should be optimized for tablets.

A possible solution would be to require a long press before entering drag-and-drop mode, similar to how iPadOS handles moving app icons on the Home Screen.

That way:

• A normal touch would open or interact with an app.

• A swipe would always scroll the page.

• Only a long press would start dragging and rearranging icons.

This would make ZimaOS much easier and more natural to use on touch devices.

[isanto1306]

Touch interaction issue in the Files app on iPad

I attached a screenshot that demonstrates the problem.

When I try to scroll through folders with my finger, the Files app often enters selection mode instead of scrolling.

As a result, a blue selection rectangle appears and multiple folders become selected, even though I only wanted to navigate through the folder list.

This happens frequently and makes the Files app difficult to use on the iPad.

Since Zima Client now officially supports iPad, I think the touch interaction should be optimized. Scrolling with a finger should never unintentionally trigger multi-selection.

A better approach would be to reserve the selection rectangle for mouse or trackpad input, while finger gestures should prioritize smooth scrolling.

[777-Spider]

Thank you very much for the detailed feedback. May I know which iPad version you are using? iPadOS 17 / 18 ？

[777-Spider]

Could you please send screenshots of these two sections? We will attempt to reproduce the issue.

[isanto1306]

I’m using an iPad Pro 13-inch (M4), 1 TB with Nano-texture glass, running iPadOS 26.5.2

[isanto1306]

I already attached screenshots of both issues in my previous posts. Are those the screenshots you mean, or are you looking for something more specific?

[777-Spider]

I have informed our development team that we will optimize the interaction here; thank you very much for your feedback.

[777-Spider]

This issue will be resolved in the next version; thank you very much for your feedback.

[777-Spider]

Is there a link?

[isanto1306]

Yes. For example, one of my custom Internet Links points to my Home Assistant instance through my reverse proxy.

The built-in IceWhale Community link opens correctly, but my own Internet Links do not open from the Zima Client.

If you need a specific example, I can provide one.

[777-Spider]

1. Please long-press the device list and use “Direct IP”; this should allow your reverse proxy to work successfully.

   

2. Regarding the web link, this is a new requirement; we will verify the technical approach. Thank you again for your detailed feedback.

[isanto1306]

I found another issue with the Direct IP feature.

The input field does not correctly save the address.

If I enter my reverse proxy URL, the value is not preserved correctly. The app automatically removes the domain and ends up keeping only https:80 (see attached screenshot).

Because of this, it is impossible to configure a reverse proxy URL.

Could you please confirm whether Direct IP is supposed to support full URLs (for example https://mydomain.example) or only plain IP addresses?

If it only supports IP addresses, then it unfortunately cannot be used with a reverse proxy setup.

[isanto1306]

I found another issue with the Direct IP feature.

Even if I enter my reverse proxy domain correctly, Zima Client automatically appends a port number (for example :80).

The problem is that I cannot remove the port. Every time I delete it and save the configuration, the app automatically adds the port back again.

For reverse proxy setups, the port should be optional because the reverse proxy already handles the routing.

At the moment, it is impossible to save my reverse proxy address without an automatically added port, which prevents this feature from working correctly.

I’ve attached another screenshot showing this behavior.

[isanto1306]

I found another issue in the Zima Client.

When I tap one of my custom Internet Links, the app displays the message:

“Currently not supported.”

The link works correctly in the ZimaOS web interface, but it cannot be opened from the Zima Client.

I’ve attached a screenshot showing the message.

If custom Internet Links are not supported yet, it would be helpful if the app clearly indicated that this feature is not yet available instead of making it appear as though the link is broken.

[isanto1306]

I have another usability suggestion for the built-in SSH terminal.

When I enable Developer Mode and connect via SSH, I often need to switch between the Zima Client and another app (for example, to copy and paste commands).

However, every time I leave the Zima Client and come back, the SSH session has already been disconnected.

I then have to reconnect, enter the username and password again, and start over.

It would be much more convenient if the SSH session remained active for a longer period, or at least while the app is running in the background. This would make copying and pasting commands much easier.

[isanto1306]

I think the Zima Client should be smarter about how it launches Docker applications.

When I connect through Zima Client, it automatically establishes a secure VPN connection to my NAS.

Because of that, the client already has secure access to my home network.

In this situation, I would expect the client to automatically choose the best way to open each application:

• If a reverse proxy URL is configured, use the reverse proxy.
• If no reverse proxy is configured, use the local NAS IP address through the VPN tunnel.

The VPN already provides secure access, so users should not have to manually switch between different connection methods.

This would make the experience much more seamless, especially for users who have a mix of applications with and without a reverse proxy.