[Solved] iMazing iOS app crashes
using eblocker 2.56, lists from 23.10.2020 on a raspi 4 in auto network mode, the DNS firewall is off.
The certificate is installed correct.
The client Mac OS X Catalina with the eBlocker set as gateway and the 188.8.131.52. as DNS Server.
When starting Imazing, an administration tool for iPhone, iPad etc the app crashes with the error seen in the screenshot.
I talked to the imazing support, they told api.amazing.com must be reachable. This was defined in trusted apps.
I did a manual diagnosis, this did not show any other communication.
Does anyone use imazing, or understands the error message?
Seems that the Controlbar gets introduced into the app.
Make sure, that the Controlbar for your device is configured to be shown in browsers only.
On your device go to Dashboard (eBlocker.box) make sure the tile "Controlbar" is shown. In the tile activate "Show only in standard web-browsers".
@random I am sorry it did not solve the problem.
First I set as you told, it crashes again.
Second I disabled the control bar, the same, I get the crash screen.
@andreas-vieringme-com Are you sure it's the same error?
Your above screenshot shows some code of the Controlbar. If CB is disabled this code should not be present (or it's a bug 😉).
Would you please share screenshot of this (new?) error. Make sure to clear cache (especially safari), kill all apps and reboot.
If you still get errors: Have you checked what might get blocked with settings>blocker>Analysis Tool ? You can try to add all the listed domains to your trusted app (and make sure app is enabled).
sorry, could not select two screenshots
@andreas-vieringme-com Have you added the listed domains to your other trusted app (and enabled the app)?
Please check the „PS“ in this post to lern how to post multiple documents/screenshots https://eblocker.org/community/announcements/before-posting-here-please-read/#post-117
Does it work if Pause is enabled (via Dashboard)?
@random adding the two domains to a trustet app, and activating did not have any effect.
Pausing the eBlocker before starting the program helps.
I tested the network traffic with wireshark and did not find any other effected domain. This correspondents with the answer from imazing support, the software only contacts api.imaging.com.
@andreas-vieringme-com Sounds odd that eBlocker‘s Controlbar get‘s integrated into the app, if all domains used for communication are on a trusted app. Maybe they are not using HTTPS to load but unsecured HTTP?! Then this approach will fail.
Nevertheless, if the CB is disabled for the device (as you stated above) I have no idea how this could throw an error. @bpr any ideas here?
@andreas-vieringme-com Make sure to not use cloaking when using the app. Have you tried to add all the domains in the dashboard tile „Tracker and Adblock Rules“ as „allowed“ domains.
@benne yes, CP is disabled and the app produces the mentioned error.
I tried both, adding the domains as a trusted app in the EB admin settings and as trusted domains in the dashboard.
Cloaking disabled or enabled did have no effect.
They released a new amazing version.
This version works fine together with eBlocker.
@kalle thanks for the info. The new version of imazing fixes the mentioned problem.