Eclipse Dark Mode (iOS 12) compatibility

[Obyboby]

After a bit of troubleshooting I have tracked down an issue with Eclipse Dark Mode (iOS 12) that seems to prevent NextUp2 from showing up in the lockscreen. As soon as the Eclipse dylib is disabled (Eclipse.dylib specifically), NextUp2 starts working again. I should mention that I'm 99% sure that Eclipse is the culprit, I have made multiple tests and ColorFlow4 seemed to be responsible for the issue at first, but after other tests I have found Eclipse to be the real cause. Hopefully this is correct.

Device is iPhone XS GSM, iOS 12.1.2 build 16C104, using Chimera 1.0.4.

Here's my complete tweaks list (Exported with "User" setting in Sileo, some core packages have been filtered out):

APT 1.8 (apt-key): 1.8.0 APT 1.8 Strict: 1.8.0 APT 1.8 Strict (lib): 1.8.0-sileo2 AdBlock for YouTube: 1.0.7 AirPort: 1.0.5-1 AnimationsBeFast: 1.4.7 Animore: 1.0.0 Aporeo: 2.4 AppList: 1.5.15-beta1 AppStore++: 0.9-12 Arkrome: 1.012 Asteroid: 3.0.4 AudioRecorder XS (iOS 12): 3.0-78 AudioSnapshotServer: 1.0.0 AutoUnlockX: 1.0.4 Barmoji: 1.9 Base Structure: 1-5 Berkeley DB: 6.2.23-2 BioProtect XS (iOS 12): 4.0-71 Bohemic Noir: 1.0 Bolders: 1.2.2-2 Bourne-Again SHell: 4.4.18-1 CCSupport: 1.2-3 CallBar XS (iOS 12): 2.2-5 CallBlocker: 1.2 Cephei: 1.13.1-2 Cercube for YouTube: 4.2.4 ChromaHomeBarX: 0.4 Clean Tab: 0.0.2 ColorBadges (Packix): 1.3.2 ColorFlow 4 (iOS 11 – 12): 1.2.3 ColorHomeBar: 0.0.3 Copypasta: 0.1.4 Core Utilities: 8.30 Core Utilities (/bin): 8.30 Cr4shed: 2.0.8 Cuboid: 0.1.1 Cydia Compatibility Package: 2.2 Cylinder: 1.0.7-beta1 Darwin Tools: 1-7 Debian Packager: 1.19.4-1 Debian Utilities: 4.8.4-1 Diff Utilities: 3.7 EVELYN's Repo Icons: 1.0-3 EW.WdgtPack.16: 1.0 EW.WdgtPack.18: 1.0 EW.WdgtPack.2: 2.0 Eclipse Dark Mode (iOS 12): 6.1 Edge: 1.0b3-10 Eveho: 1.0 Eyeplugs: 1.5.1 Filza File Manager 64-bit: 3.7.0-18 Find Utilities: 4.6-1 Five Icon Dock (iOS 11 & 12): 1.0 GNU Privacy Guard: 1.4.23 Gesto: 1.3.1 Groovify: 1.1-2 HS.Ryu_007 Animated Gradient Pack: 1.0.0 InvisibleQAButtons: 0.0.2 LS EW.Battery: 1.0 LS EW.Legacy: 1.0 LeaveMeAlone: 2.3.1 Liberty Lite (Beta): 0.2.12 LibreSSL: 2.8.3 Light: 1.2 Limelight: 1.9.6 Lisa: 1.0.2 Lotus: 1.0 Lotus Dark: 1.0.8 Lumi: 1.0.0 MiscSettings: 2.4.1 Miso: 1.0 Missito: 0.1.4 Mitsuha Infinity: 0.1.5-1 NFCWriter XS: 2.0-8 Nereid: 0.1.7 New Curses: 6.1-1 NewTerm 2 (iOS 7 – 12): 2.1 NextUp 2 beta (iOS 12): 1.0-beta8 Nghttp2: 1.37.0 Noctis12: 1.6.5 NotJellyfish: 2.0.2 Notchification: 1.5-7 Notifica: 0.2.8-2 OpenSSH: 7.9p1 Ore: 1.1.1 Overcast: 1.1 PencilChargingIndicator: 1.2-b6 PowerModule: 1.2.4-2 Profile Directory: 0-3 ReProvision: 0.4.2 Relocate: 0.1.10 SB EW3: 1.0 Safari Plus: 1.6.8-3 Saw: 1.3.4 Shadow: 1.13 Shy Labels: 1.1.1 Sileo: 1.0.9 SnapBack (BETA): 1.0.4 Snapper 2: 2.1 SnowBoard: 1.1.7 Sonus12: 1.2.0-1 Strings: 1.0.0 Substitute: 0.1.0-coolstar Substrate Compatibility Layer: 99.2 Succession: 1.3.2 System Info: 2.2.1-10+debug TapVideoConfig: 0.0.4.1 Tape Archive: 1.31-1 Tweak Injector: 1.1.1-sileo UnSub: 0.1.9 Veexillum: 2.7 Viola: 1.2 Weather12: 1.3.0 WeatherPanel: 0.4 WeatherPanelV2: 0.2 XZ Utils: 5.2.4-1 Xen HTML: 0.5.2 XenInfo: 2.2.5 Xenimated: 1.0 Zebra (BETA): 1.0-beta11 bzip2: 1.0.6-2 cURL: 7.64.1-1 grep: 3.3 gzip: 1.10 iCleaner Pro: 7.7.5 iPhone Firmware (/sbin): 0-1 libCSColorPicker: 1.0.3 libCSPreferences: 1.1.6 libCercube: 1.1.1 libbulletin: 0.1-147 libmitsuha: 0.1.7 libnepeta: 0.1.1 libswift4: 4.2.1-2 sed: 4.7 shell-cmds: 203-2 shuffle: 1.0.1b sourceutility: 0.8.3.1 system-cmds: 790-2

[Nosskirneh]

Hi!

Thanks for reporting! However, I can't seem to reproduce the issue (either with only Eclipse or with combination with ColorFlow 4). Do you know if there is any specific setting in either tweak that's causing this?

[Obyboby]

Hi Andreas,

Thanks for contacting me. After opening the issue, I've had issues with other tweaks not working properly with Spotify, so I proceeded to disable the various dylibs via iCleaner to find the reason for that, and I ended up noticing that COLORFLOW 4 seems to actually be preventing NextUp2 from working. I am really confused with this (as you may be as well) because at first it seemed to be COlorflow, then you told me that it was working fine for you, so I tried again and the second time Eclipse seemed to break NextUp. Now it's Colorflow again. Since disabling it, I can run all my tweaks fine and yours works perfectly as well. I don't really know what to do at this point, since Colorflow is causing issues on my device but apparently it is supported by NextUp2. Keep in mind that I paid for all my tweaks and I do not use cracked software. If there's anything I can do to help you figure if Colorflow really has issues with your tweak, I'd be happy to help. I am just confused as to why the other time it was Eclipse breaking it. Thanks

Roberto

On Thu, Jun 6, 2019 at 9:30 PM Andreas Henriksson notifications@github.com wrote:

Hi!

Thanks for reporting! However, I can't seem to reproduce the issue (either with only Eclipse or with combination with ColorFlow 4). Do you know if there is any specific setting in either tweak that's causing this?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/Nosskirneh/NextUp-Public/issues/23?email_source=notifications&email_token=ACVSFTQMEJEWS4B73A72MY3PZFQWJA5CNFSM4HQJ6H3KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODXD5J4Q#issuecomment-499635442, or mute the thread https://github.com/notifications/unsubscribe-auth/ACVSFTX6OGRKZVNXMB2QOODPZFQWJANCNFSM4HQJ6H3A .

[Obyboby]

Oh yeah, I did not realize that you already mentioned trying Colorflow as well. For the record, I have even tried completely disabling Colorflow in my lockscreen but the issue persists. I honestly don't know what else I can try at this point. I don't mind giving up Colorflow but keeping it active would obviously be the best scenario.

[Nosskirneh]

Sorry for the late answer!

It sounds to me like it's neither ColorFlow or Eclipse to blame, but rather a coincidence with something else that makes it not showing up seemingly random. NextUp is heavily dependent on RocketBootstrap, and I've heard users solving similar problems by reinstalling it (it sounds weird, I know :P)

Also, please disable the "Hide on Empty" setting in NextUp to rule out the case when NextUp's client code considers the queue to be empty.

It's difficult to say exactly what is happening. If you're tech savy, I would recommend installing some FLEX instance (such as FLEXing, FLEXit etc), invoke it in SpringBoard when playing music, go to "System Libraries" -> "NextUp.dylib", go into NextUpManager, "Live Instances" and take only one (and it's object if you're using a new FLEX instance that wraps everything in a FLEX object). If the bundle ID of the media app is mediaApplication and can also be found within enabledApps, and if the metadata holds data then the RocketBootstrap connection works fine and it's something else.

I wished I could give you a more helpful answer but it's unfortunately impossible without being able to reproduce the issue.

Please let me know how it goes.