[Magisk] AdrianShepherd:
I'm having an issue with Magisk Manager modules not showing in my app drawer or anywhere else.

I have Magisk v18.1 and Magisk Manager v7.0.0 on my Samsung A3 2016 (A310F) running Android 7.0, SafetyNet passed.

I can download and install modules from Magisk Manager, however after reboot there is no sign of the app on the phone. The Downloads and Modules sections of Magisk Manager both show that the requested apps are installed.

I have TWRP Recovery, and have tried installing from the Recovery menu, however that doesn't work either.

All modules have this problem, I have tried it with several different ones.

I have also tried reinstalling Magisk as a direct installation from Magisk Manager, creating a MagiskManager folder on my internal storage, disabling the native YouTube app, none of which has worked.

These are the logs that I could find on my device:

MAGISK INSTALL LOG:

- Copying zip to temp directory

- Installing App_Systemizer_(Terminal_Emulator)-v16.2.zip

- Mounting /system, /vendor

Archive: /data/user/0/com.topjohnwu.magisk/cache/install.zip

creating: common/

inflating: common/aapt

inflating: common/file_contexts_image

inflating: common/mod-util.sh

inflating: config.sh

inflating: module.prop

*******************************

Terminal App Systemizer

by veez21 @ xda-developers

*******************************

******************************

Powered by Magisk (@topjohnwu)

******************************

- Creating /data/adb/magisk_merge.img with size 64M

Creating filesystem with parameters:

Size: 67108864

Block size: 4096

Blocks per group: 32768

Inodes per group: 4096

Inode size: 256

Journal blocks: 1024

Label:

FLEX_BG size: 0

Blocks: 16384

Block groups: 1

Reserved block group size: 0

Created filesystem with 11/4096 inodes and 1286/16384 blocks

Create /data/adb/magisk_merge.img with size 64M

e2fsck 1.42.9 (28-Dec-2013)

- Extracting module files

Archive: /data/user/0/com.topjohnwu.magisk/cache/install.zip

creating: system/

creating: system/xbin/

inflating: system/xbin/systemize

- Setting permissions

- Done

MAGISK LOG:

02-17 14:24:30.020 2206 2206 I Magisk : * Creating /sbin overlay

02-17 14:24:30.130 2208 2208 I Magisk : * Device API level: 24

02-17 14:24:30.130 2208 2208 I Magisk : Magisk v18.1(18100) daemon started

02-17 14:24:30.131 2208 2209 I Magisk : ** post-fs-data mode running

02-17 14:24:30.131 2208 2209 I Magisk : * Initializing Magisk environment

02-17 14:24:30.139 2208 2209 I Magisk : * Mounting mirrors

02-17 14:24:30.141 2208 2209 I Magisk : mount: /sbin/.magisk/mirror/system

02-17 14:24:30.141 2208 2209 I Magisk : link: /sbin/.magisk/mirror/vendor

02-17 14:24:30.143 2208 2209 I Magisk : bind_mount: /sbin/.magisk/mirror/bin

02-17 14:24:30.146 2208 2209 I Magisk : * Setting up internal busybox

02-17 14:24:30.203 2214 2214 I Magisk : Magisk v18.1(18100) logger started

02-17 14:24:30.265 2208 2209 I Magisk : * Running post-fs-data.d scripts

02-17 14:24:30.366 2208 2209 I Magisk : Upgrade/New module: terminal_systemizer

02-17 14:24:30.367 2208 2209 I Magisk : Create /data/adb/tmp.img with size 64M

02-17 14:24:30.796 2208 2209 I Magisk : * Merging /data/adb/magisk_merge.img + /data/adb/magisk.img -> /data/adb/tmp.img

02-17 14:24:30.916 2208 2209 I Magisk : * Move /data/adb/tmp.img -> /data/adb/magisk.img

02-17 14:24:30.917 2208 2209 I Magisk : * Mounting /data/adb/magisk.img

02-17 14:24:30.968 2208 2209 I Magisk : * Running module post-fs-data scripts

02-17 14:24:30.968 2208 2209 I Magisk : * Loading modules

02-17 14:24:30.968 2208 2209 I Magisk : terminal_systemizer: constructing magic mount structure

02-17 14:24:30.969 2208 2209 I Magisk : mnt_tmpfs : /system/xbin

02-17 14:24:30.969 2208 2209 I Magisk : bind_mount: /system/xbin/systemize

02-17 14:24:30.969 2208 2209 I Magisk : bind_mount: /system/xbin/cpustats

02-17 14:24:30.970 2208 2209 I Magisk : bind_mount: /system/xbin/dexlist

02-17 14:24:30.970 2208 2209 I Magisk : bind_mount: /system/xbin/jack_connect

02-17 14:24:30.970 2208 2209 I Magisk : bind_mount: /system/xbin/jack_disconnect

02-17 14:24:30.970 2208 2209 I Magisk : bind_mount: /system/xbin/jack_lsp

02-17 14:24:30.970 2208 2209 I Magisk : bind_mount: /system/xbin/jack_showtime

02-17 14:24:30.970 2208 2209 I Magisk : bind_mount: /system/xbin/jack_simple_client

02-17 14:24:30.970 2208 2209 I Magisk : bind_mount: /system/xbin/jack_transport

02-17 14:24:31.000 2208 2256 I Magisk : * Starting MagiskHide

02-17 14:24:31.000 2208 2256 I Magisk : hide_utils: Hiding sensitive props

02-17 14:24:31.012 2208 2256 I Magisk : hide_list: [com.google.android.gms/.droidguard.DroidGuardService]

02-17 14:24:31.812 2208 2309 I Magisk : ** late_start service mode running

02-17 14:24:31.814 2208 2309 I Magisk : * Running service.d scripts

02-17 14:24:32.342 2208 2309 I Magisk : * Running module service scripts

02-17 14:25:29.051 2208 2256 I Magisk : proc_monitor: com.google.android.gms/.droidguard.DroidGuardService PID=[5327] ns=[4026539997]

02-17 14:26:30.072 2208 2256 I Magisk : proc_monitor: com.google.android.gms/.droidguard.DroidGuardService PID=[9575] ns=[4026540017]

02-17 14:27:27.018 2208 2256 I Magisk : proc_monitor: com.google.android.gms/.droidguard.DroidGuardService PID=[12050] ns=[4026539997]

02-17 14:27:27.142 2208 2256 I Magisk : proc_monitor: com.google.android.gms/.droidguard.DroidGuardService PID=[12071] ns=[4026539999]

TWRP RECOVERY LOG:

I'm happy to post this if needed, however it's very long and I didn't want to make this hard to read.

What can I do to fix this installation issue?