Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Mode update not shown correctly in Contribution Manager #640

Closed
hkiel opened this issue Jan 18, 2023 · 5 comments
Closed

Mode update not shown correctly in Contribution Manager #640

hkiel opened this issue Jan 18, 2023 · 5 comments
Labels
High Priority Very high priority and would like to fix ASAP

Comments

@hkiel
Copy link
Contributor

hkiel commented Jan 18, 2023

Description

I just installed new processing 4.1.2 with a pending update of Android mode.
I open the Modes Manager via drop down menu and do not see the Android mode in the list of modes (though it is installed).
Also in "Updates" tab "Timer" Library pretends to be updateabe (but with installed 1.0.1 vs. available 1.0.1 versions)

Timer is neither installed on my setup nor is it updateable. Looks like the index of updateable Android mode is used on Libraries list, showing the wrong thing.

Steps to Reproduce

see above

Your Environment

  • Processing version: 4.1.2
  • Operating System and OS version: win10
@benfry
Copy link
Owner

benfry commented Jan 18, 2023

Can you post a screenshot of what the “Updates” tab looks like in this setup?

Also, would you mind posting a zip of the Android Mode that needed to be updated so I can try to reproduce this?

@hkiel
Copy link
Contributor Author

hkiel commented Jan 18, 2023

Processing 4.1.2 main window with update indicator:
p4_main

I select "Manage modes" menu and see that there is a mode "Timer" which is actually a library. This should really be "Android Mode".
p4_modes

Same name mismatch on the update tab:
p4_update

Here is the old Android mode zip:
AndroidMode.zip

@benfry
Copy link
Owner

benfry commented Jan 18, 2023

Great thanks; as suspected, that was something I saw show up while I was working on 4.1.2 all weekend… Thought I had a workaround for it, but it looks like it needs a more thorough fix.

@benfry benfry added the High Priority Very high priority and would like to fix ASAP label Jan 19, 2023
@benfry benfry closed this as completed in 40611e6 Jan 20, 2023
@benfry
Copy link
Owner

benfry commented Jan 20, 2023

Ok, I think we're set for 4.1.3… Will try to push that release out shortly, just a few things remaining to tidy up.

@github-actions
Copy link

This issue has been automatically locked. To avoid confusion with reports that have already been resolved, closed issues are automatically locked 30 days after the last comment. Please open a new issue for related bugs.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Feb 19, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
High Priority Very high priority and would like to fix ASAP
Projects
None yet
Development

No branches or pull requests

2 participants