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

Error: NG02100 #3887

Closed
joeax910 opened this issue Jan 11, 2025 · 3 comments
Closed

Error: NG02100 #3887

joeax910 opened this issue Jan 11, 2025 · 3 comments

Comments

@joeax910
Copy link

joeax910 commented Jan 11, 2025

Steps to Reproduce

  1. Install version 11.1.1 through f-droid.
  2. Run the app for the first time and tap on the "Let's go!" button to start the tutorial.
  3. Tap on the button with the +.
  4. Enter a title (e.g. "Test") and tap the "Go" key on the software keyboard.
  5. Close the Add Task bar by tapping anywhere on the grayed out backdrop.
  6. Tap the play button in the top right corner to start the time tracking.
  7. Wait a couple of seconds or a full minute, it doesn't matter.
  8. Tap the same button (now with a pause sign) in the top right corner to stop the time tracking.
  9. Tap on the previously created task (named "Test", or whatever).
  10. An error message for NG02100 is shown (see provided screenshot)
    Screenshot_20250112_003909_Super Productivity

Meta Info

META: SP11.1.1_L2A __ Browser – sv-SE – Linux aarch64 – Mozilla/5.0 (Linux; Android 14; SM-A528B Build/UP1A.231005.007; wv) AppleWebKit/537.36 (KHTML, like Gecko) Version/4.0 Chrome/131.0.6778.201 Mobile Safari/537.36

Stacktrace

invalidPipeArgumentError (https://localhost/node_modules/@angular/common/fesm2022/common.mjs:4318:9)
formatDate (https://localhost/node_modules/@angular/common/fesm2022/common.mjs:4807:14)
pureFunction2Internal (https://localhost/node_modules/@angular/core/fesm2022/core.mjs:31834:116)
ɵɵpipeBind2 (https://localhost/node_modules/@angular/core/fesm2022/core.mjs:32042:40)
ɵɵpipeBind2 (https://localhost/src/app/features/tasks/task-detail-panel/task-detail-panel.component.html:305:9)
setSelectedIndex (https://localhost/node_modules/@angular/core/fesm2022/core.mjs:12864:4)
setBindingIndex (https://localhost/node_modules/@angular/core/fesm2022/core.mjs:14449:6)
isExhaustiveCheckNoChanges (https://localhost/node_modules/@angular/core/fesm2022/core.mjs:14658:4)
viewAttachedToChangeDetector (https://localhost/node_modules/@angular/core/fesm2022/core.mjs:14620:2)
detectChangesInComponent (https://localhost/node_modules/@angular/core/fesm2022/core.mjs:14609:2)

Actions Before Error

1736636720173: [Persistence] Save to DB (3) 
1736636721165: [Task] Add time spent 
1736636721168: [Project] Update Work End 
1736636721170: [Tag] Update Work End for Tag 
1736636721172: [Persistence] Save to DB (3) 
1736636722165: [Task] Add time spent 
1736636722169: [Project] Update Work End 
1736636722170: [Tag] Update Work End for Tag 
1736636722172: [Persistence] Save to DB (3) 
1736636723165: [Task] Add time spent 
1736636723168: [Project] Update Work End 
1736636723169: [Tag] Update Work End for Tag 
1736636723170: [Persistence] Save to DB (3) 
1736636724166: [Task] Add time spent 
1736636724172: [Project] Update Work End 
1736636724173: [Tag] Update Work End for Tag 
1736636724176: [Persistence] Save to DB (3) 
1736636725165: [Task] Add time spent 
1736636725171: [Project] Update Work End 
1736636725173: [Tag] Update Work End for Tag 
1736636725176: [Persistence] Save to DB (3) 
1736636726165: [Task] Add time spent 
1736636726170: [Project] Update Work End 
1736636726173: [Tag] Update Work End for Tag 
1736636726175: [Persistence] Save to DB (3) 
1736636726275: [Task] Toggle start 
1736636726276: [Persistence] Save to DB 
1736636726276: [Task] UnsetCurrentTask 
1736636739734: [Task] SetSelectedTask 
1736636739736: [Layout] Hide Notes
Copy link

Thank you very much for opening up this issue! I am currently a bit overwhelmed by the many requests that arrive each week, so please forgive me, if I fail to respond personally. I am still very likely to at least skim read your request and I'll probably try to fix all (real) bugs if possible and I will likely review every single PR being made (please, give me a heads up if you intent to do so) and I will try to work on popular requests (please upvote via thumbs up on the original issue) whenever possible, but trying to respond to every single issue over the last years has been kind of draining and I need to adjust my approach for this project to remain fun for me and to make any progress with actually coding new stuff. Thanks for your understanding!

Copy link

Hello there joeax910! 👋

Thank you and congratulations 🎉 for opening your very first issue in this project! 💖

In case you want to claim this issue, please comment down below! We will try to get back to you as soon as we can. 👀

For more open ended discussions and/or specific questions, please visit the discussions page. 💖

@joeax910
Copy link
Author

Might have been the same issue as #3842, and either way, the bug seems to be fixed by version 11.1.2. Thanks! :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant