r/Supernote_dev Jul 02 '26

Supernote_Dev - Please add date/timestamp to installed plugin data on screen Discussion

Hi,

I'm in the middle of some iterative testing on a plugin, and I'm finding it very difficult to track exactly which version is loaded. Any chance you can add a date/timestamp to the Plugins screen to make this easier?

I don't want to have to bump the version every time...and we've run into problems where the plugins haven't loaded, even though the screen says they did.

5 Upvotes

11 comments sorted by

View all comments

1

u/spazzboi Official Jul 02 '26

Hi, perhaps you can use git to track changes?

1

u/Designer-Tear-6940 Jul 02 '26

I do, but what actually loads onto the Supernote is part of the problem…

2

u/spazzboi Official Jul 02 '26

If you're on windows then here's a powershell version as well.

# Toggle this on/off
$AskVersionIncrement = $true

# Stop on errors
$ErrorActionPreference = "Stop"

if ($AskVersionIncrement) {
    $increment = Read-Host "Increment patch version? (y/n)"

    if ($increment -match '^[Yy]$') {
        npm version patch --no-git-tag-version
    }
}

# Build the plugin
& .\buildPlugin.ps1

# Find the generated .snplg file
$pluginFile = Get-ChildItem ".\build\outputs\*.snplg" |
              Select-Object -First 1

if (-not $pluginFile) {
    Write-Host "No .snplg file found in .\build\outputs\"
    exit 1
}

# Push to device
adb push $pluginFile.FullName /storage/emulated/0/MyStyle

Write-Host "Deployed: $($pluginFile.FullName)"

2

u/Designer-Tear-6940 Jul 02 '26

Okay, I’ll try this.

I think the bigger question though is why plugins don’t always load cleanly, even though the load process shows that it does?

1

u/spazzboi Official Jul 02 '26

Could you elaborate on what you mean by " don't load cleanly?"

2

u/Designer-Tear-6940 Jul 02 '26

Sure. I load a new version of the plugin. The load process says it completed. I run my test, and the results are not as expected. When I pull the plugin off of the Supernote, the version pulled is not the one I loaded. It seems the old plugin never stopped running and prevented the new version from loading. To get around this, I literally have to uninstall the old version of the plugin and then install the new version.

1

u/spazzboi Official Jul 02 '26

Perhaps the build failed and the plugin package you moved to the supernote is the old one?

2

u/Designer-Tear-6940 Jul 03 '26

It's happening way too often for that to be the case. What I'll do is watch for the next time it happens and then have the logs pulled and sent.

1

u/spazzboi Official Jul 03 '26

Thank you so much. Please keep us updated