portapps/discord-portable

Discord 1.0.9001

Closed this issue ยท 13 comments

Update for 1.0.9001
Previous updates, the internal updater, worked as portable, but with this newest discord update, the portapps launcher will launch the older version of discord, and despite 1.0.9001 installing to the portable folder, it puts all appdata in roaming etc.

discord-portable.log

@Chaython Thanks for your feedback. Looks like main module has been updated from 0.0.309 to 1.0.9001 silently. We'll make the update soon. Keep you in touch.

@Chaython Thanks for your feedback. Looks like main module has been updated from 0.0.309 to 1.0.9001 silently. We'll make the update soon. Keep you in touch.

Sorry to bother, but you, probably, forgot about it =)

Working on it guys. I have two issues with v1.x.x of Discord atm:

  • Handle installer.db to be able to manage versioning without crashing portability
  • Handle new native updater (updater.node) and squirrel updater to skip host update

I have managed to fix the first issue last week. Needs to fix the last one and will be good to create a release.

@maxstlk

Sorry to bother, but you, probably, forgot about it =)

I've got an enhanced dashboard to handle all my backlog across GitHub with priorities so no I'm aware of this but I've got many projects to maintain. So please be patient or contribute. Thanks.

@maxstlk

Sorry to bother, but you, probably, forgot about it =)

I've got an enhanced dashboard to handle all my backlog across GitHub with priorities so no I'm aware of this but I've got many projects to maintain. So please be patient or contribute. Thanks.

No problem man, take your time!

Take ur time and do ur best, man!
We'll waiting, ur project helped a lot of internet cafe here!

Using a pinned manifest to "disable" auto-update seems to work for now. Can you try https://github.com/portapps/discord-portable/releases/tag/1.0.9002-9? Thx.

Screenshot (1)
Is it normal to update it?

@fahmiyufrizal

Is it normal to update it?

Yes this is just the modules not host update (aka core).

Screenshot (2)
I think it's working

@fahmiyufrizal Great, let's wait for the next iteration (1.0.9003) to see if pinned manifest still works.

1.0.9003 is here now