模块重启挂载不上 about com.piyushgarg.rclone HOT 11 CLOSED

@muablog, is your device rooted?
Never had this problem.
Go into adb shell and try su command?

from com.piyushgarg.rclone.

哪个版本的Magisk? 如果你会说英语，那么帮助你会更容易。

from com.piyushgarg.rclone.

Magisk and modules are up to date

from com.piyushgarg.rclone.

哪个版本的Magisk？如果你会说英语，那么帮助你会更容易。

Magisk and modules are up to date

from com.piyushgarg.rclone.

@muablog，你的设备是否已植根？
从未遇到过这个问题。
进入adb shell并尝试su命令？

It's root.，And try the Su command

from com.piyushgarg.rclone.

It's strange. I find I don't know when it's already mounted.

from com.piyushgarg.rclone.

@muablog What is your mount namespace in Magisk Manager settings set as? Are you saying it works sometimes and not others?

from com.piyushgarg.rclone.

I think he is suffering from the same problem I am.

Translated by Google (surprisingly understandable):

Hello, the module will not be automatically mounted after rebooting, and I try to mount it manually and it can't mount it, only the empty folder

The module does not automatically mount upon reboot and needs to be reinstalled.

@muablog For now, try reinstalling the module. It works for me.
目前，请尝试重新安装模块。 这个对我有用。

from com.piyushgarg.rclone.

@HASJ I wonder if somehow my updates to dev branch are ending up being delivered prematurely. You said the August 2nd fixed your issues... I just pushed that to my dev branch which shouldn't be available through Magisk Manager.

If users decide to regularly grab things like the service.sh and place them in your module undirected that's not something I can support. Even if I have told you once before to do so. The dev dranch should be considered unfinished & I only merge into our master (avail through MM) when I think it's okay to be available to general public. At least that's supposed to be the theory. If Magisk Manager is grabbing from dev before I merge into master then I'm going to have to look into it.

from com.piyushgarg.rclone.

I do believe that is the case, @Geofferey.

At first it seemed intentional, as the issue I first reported and you then modified appeared on the repo almost instantly.
But since the broken update, something must be wrong.

And don't worry, I am not using any separate file from the dev branch, only those from the repo (which might be the dev branch, now that I think about it 😐)

from com.piyushgarg.rclone.

Yup, this issue seems in part due to they way modules repo operates. Whenever I push changes to the dev branch Magisk Manager catches the time last changes were made to repo and thinks there is an update even tho there isn't.

The module itself isn't broken but when the same version updates over itself it breaks for some reason. I'm gonna look and see what's wrong with Module itself because that shouldn't happen even if it's updating over same version.

I honestly thought Magisk Manager was only supposed to show updates for a module if it's version code changed. Appears that is not the case :( . I guess I'll have to move all development over to my fork which kinda sucks because I like users to see progress being made before release.

from com.piyushgarg.rclone.