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

Main page tabs aren't what they should be after import before restart #3312

Closed
PeterHindes opened this issue Mar 30, 2020 · 20 comments
Closed
Labels
bug Issue is related to a bug GUI Issue is related to the graphical user interface

Comments

@PeterHindes
Copy link
Contributor

PeterHindes commented Mar 30, 2020

Imported data is only updated after restart of NewPipe.
After importing data from an older version with a different tab arrangement, the taps will not contain the screen they should. Haven't tested with data from the current version. Fix is simple. Close the app and relaunch after importing. The app can do this its self to prevent user jank.

Different tab arrangement:
image

@PeterHindes PeterHindes added the bug Issue is related to a bug label Mar 30, 2020
@mauriciocolli
Copy link
Contributor

I'm not able to replicate this, can you post more detailed steps to reproduce it like the bug report template indicates?

@PeterHindes
Copy link
Contributor Author

Sorry about that.
Steps

  1. Install older version of newpipe
  2. Use settings to change which tabs show on top
  3. Export settings from old version of newpipe
  4. Install newest newpipe.
  5. import settings
  6. return to the home screen and see that they are not what the icon says they are. Unitll
  7. Restart the app
  8. They behave normaly now.

@gkeegan
Copy link
Contributor

gkeegan commented Mar 30, 2020

I have noticed odd behavior with the import as well when changing the tabs. Can confirm this is (or at least was, but I don't see commits that say it was fixed) a bug.

@PeterHindes
Copy link
Contributor Author

I tested it on a build of the code from the dev branch

@PeterHindes
Copy link
Contributor Author

Should be a simple fix to restart the app on import of settings.

@mauriciocolli
Copy link
Contributor

@PeterHindes

You can see in this absolute bad practice of a class that the app is, indeed, restarted. In my case, the app is restarted and all the tabs are what they should be, in various Android versions as well.

About that screenshot that you posted, the name and the icon match what it should be. Please, post screenshots before and after importing so we can see the difference.

But by what you just said above:

Should be a simple fix to restart the app on import of settings.

And,

  1. import settings
  2. return to the home screen and see that they are not what the icon says they are. Unitll

Most probably the app is not restarting due to something specific to your device, you shouldn't be able to just return to the home screen.

Is that it? The app doesn't restart at all after confirming the two dialogs?


@gkeegan

Can confirm this is (or at least was, but I don't see commits that say it was fixed) a bug.

Please, post the before/after screenshots too. And does the app restart at all for you?

@gkeegan
Copy link
Contributor

gkeegan commented Mar 31, 2020

I can't do screenshots since I'm on 0.19.0 and afraid to import data since it is apparently broken or something. What I remember is that it shows trending when it is supposed to be the channel list with the "whats new" bar at the top. What was supposed to be bookmarks because that page instead.

@gkeegan
Copy link
Contributor

gkeegan commented Mar 31, 2020

It did restart when I did it yes.

@PeterHindes
Copy link
Contributor Author

I am running it in the android emulator on andorid r and on a oneplus 6t on android 10

@PeterHindes
Copy link
Contributor Author

Ill try to collect screen shots in a little while

@mauriciocolli
Copy link
Contributor

Oh, now I managed to replicate the bug. Will fix it shortly.

@Stypox Stypox changed the title [Minor Bug] Screens aren't what they should be after import before restart. Main page tabs aren't what they should be after import before restart May 22, 2020
@Stypox Stypox mentioned this issue May 22, 2020
5 tasks
@B0pol B0pol mentioned this issue Jul 9, 2020
@opusforlife2
Copy link
Collaborator

Still true as of 0.19.8.

@opusforlife2
Copy link
Collaborator

Some (accidental?) progress on this: If you uninstall an APK, reinstall it, then import database, Newpipe immediately shows the correct main page tabs, and also shows a toast saying the language will be changed on app restart (if that setting has been changed from the default).

But for some reason, this does not happen for completely new APKs.

@PeterHindes Could you confirm if this is the case for you?

@PeterHindes
Copy link
Contributor Author

Some (accidental?) progress on this: If you uninstall an APK, reinstall it, then import database, Newpipe immediately shows the correct main page tabs, and also shows a toast saying the language will be changed on app restart (if that setting has been changed from the default).

But for some reason, this does not happen for completely new APKs.

@PeterHindes Could you confirm if this is the case for you?

I don't have the original testing environment I was using. Sorry.

@opusforlife2
Copy link
Collaborator

@PeterHindes Sorry, I didn't get it. What testing environment? To be clear, I'm talking about the current release of Newpipe.

@PeterHindes
Copy link
Contributor Author

@PeterHindes Sorry, I didn't get it. What testing environment? To be clear, I'm talking about the current release of Newpipe.

I installed a different rom on my phone and haven't been using NewPipe. I don't have my old save data.

@opusforlife2
Copy link
Collaborator

I just installed a brand new debug APK (from #6673), and it was able to successfully import the database and run on the first try. Seems like this problem is fixed. I want to test one or two more new debug APKs before closing this, though.

@XiangRongLin
Copy link
Collaborator

It's probably because of #6639.

Now the db is closed before the import and gets reopened on the new db.

@opusforlife2 opusforlife2 linked a pull request Aug 11, 2021 that will close this issue
@opusforlife2
Copy link
Collaborator

This was actually fixed by #6639, but that's already merged, so I linked it to the Release PR instead.

@opusforlife2 opusforlife2 removed a link to a pull request Aug 14, 2021
@opusforlife2
Copy link
Collaborator

Actually, fixed by #6495 in a previous release. Closing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Issue is related to a bug GUI Issue is related to the graphical user interface
Projects
None yet
Development

No branches or pull requests

6 participants