Time Cop used to use the screenshot package for automated tests, but unfortunately, that package is obsolete and non-functional now.

Thankfully, Flutter 2.5 and above make it easy to take screenshots inside integration tests. It'd be useful if new tests were written to make generating screenshots easy again.

Here's a relevant article on this: https://dev.to/mjablecnik/take-screenshot-during-flutter-integration-tests-435k

And here's an example of a project using this in practice: https://github.com/wger-project/flutter/tree/feature/exercise-crowdsourcing/integration_test

Yesterday I got auto-updated by Google Play to version v1.6.0+36 (Android v8.0.0). After that my old projects disappeared the same way as described in #40.

I believe the issue is caused by incorrect scheme of projects table: https://github.com/hamaluik/timecop/blob/a69d2778c1ab1b7ef18df87488071f4861b2c902/lib/data_providers/data/database_provider.dart#L40 After DB upgrade for all old projects archived contains string false but the application expects integer there (0 or 1).

The scheme is incorrect from the application POV but I think that SQL doesn't support such tables either though I don't know SQL that much.

As a workaround I exported my DB then manually edited the scheme in sqlite editor: changed the archived field description in the projects table to the following:

archived boolean not null default 0

Then I cleared data of the application on the phone and imported modified DB file. After small delay I can now use the app again.

I'd love to see this app on F-Droid, the most popular free and open-source app store for Android.

You could submit the app to F-droid via a pull request or simply create an issue on their Gitlab Request for Packaging repository, asking for this app to be packaged.

Thank you for making this app!

There's a number of warnings throughout the code about using BuildContexts across asynchronous gaps. It'd be good to fix the underlying problems.

For information on why this is happening and how to fix it, see this video: https://www.youtube.com/watch?v=bzWaMpD1LHY

I wanted a macOS app for my own usage, even if not particularly optimized for the mouse.

I did a rudimentary port, BUT did it in a pretty ugly way — I commented out dev dependencies (not part of the commits), removed tests (also not part of the commits), and updated several dependencies (that IS part of the commits).

I can't afford to devote more time to this right now. If anyone would like to pick up where I left off, what's left to do is to bring tests in order, sort out dev dependency conflicts, and make sure everything still works as intended.

Adding support for Linux.

I would be willing to also create an accompanying Flatpak release (that's the modern distro-agnostic packaging format for Linux) on Flathub, if permitted to.

Many a time have I forgotten to leave a timer going just because I closed the application to go do something else (on the phone). If there was a notification icon that would expand to the event description (maybe also the project under which it is) and the currently elapsed time, then when it would always be there in the periphery or at the very least be something that gets reminded when the phone is opened (as the notification would be visible in the lock screen).

With "Only Allow One Running Timer at a Time" set to ON in the settings, I expect it to stop the currently running timer when I start another one by swiping left on a previous task. This does not happen, and both timer runs at the same time as a result.

Fixes #80

Following the requested changes in the issue, there were a things that needed to happen in order for the feature to work:

• A new folder called integration_test was created in the main project hierarchy
• The integration_test dependency was added under dev_dependencies
• The older screenshots_test.dart has been deleted
• Integration tests use a WidgetTester, so the older logic had to be refactored
• Since the older test relied on a timer with an id of 42, which does not exist, the logic has changed to rely on the current default timers which are running.
• This means that the test selects the first running timer (UI Layout), stops it and then clicks on it to go to the editing screen

The test has been run on an emulated device several times and appears to be working.

A video of the test running:

The current version of the flutter_bloc library that's being used is 7.3.3, but the latest version is 8.1.1.

For upkeep, it'd be good to upgrade to the latest version, including all the refactoring that takes.

Hey there,

i have issues to running this Project. I tried some stuff to run this, but nothing has fix it. Now i have already re-install this project, but the error is still there. I have the latest Ruby, flutter and Cocoapot version, but it seemy to me, there are more problems. Can you please help me with this?

Thanks a lot.

Really nice tool. One handy feature could be filter "shortcuts" to easily select often used time periods like:

• current {week,month,year} till today
• last/previous {week,month,year}

Actual: It seems that WeekdayAverages a slightly off when viewed for a time period not aligned with the start/end of a week. Thus artificially decreasing the daily average for those days for which no data is available.

Expected: WeekdayAverages only normalizes daily hours worked by the number of instances of the given weekday within the actual time period monitored.

Clockify and Toggl have a browser extension that add buttons on specific websites. This makes it easy for users to start/stop projects on the fly based on the where the button is. Example, gitlab-github buttons would automatically add the name of the issue to the timer. They use API's to their servers to start/stop timers, something Timecop does not have.

However, it should be possible to connect to a Linux desktop client via Native messaging. I have not experimented with this so I can not be certain it would work.

The Toggl Extention uses Apache License 2.0. It means that it can used, replacing their API requests to Native messaging.

This is big suggestion, and I understand this. So there is no rush. Other people can add a '👍' or '👎' if they agree/disagree.

Example Image

In my organization, we enter the work time in a form. The app would be even more useful if start and end time would be featured in the overview, possibly with a column chooser like in the reporting section.

Hi, I noticed that the latest update of Time Cop on the Play Store has been released on 2021-01-15, while the latest version on F-Droid has been released on 2022-05-18. Is it possible to update the Play Store release? (Btw, why does it cost 0.99$ if it is also on F-Droid?)