I want to create an EKevent from objective c, that spans multi-days, in both iOS 5 and iOS 6 the creation process is work as expected, and the event created successfully, but when I fetch the event from an event store the event disappear from the last day -the day that event ends on - this issue exist in iOS 6.
What do you think guys?
I also saw this issue with multi day events. I think it's a bug, so I filed a bug report with Apple about it. I worked around this issue by adjusting my event store predicate for the last day to include 11:59pm of the 2nd-to-last day. After doing that, I then manually filter out the 2nd-to-last day events, if any were pulled in.
Related
I have a simple application, to which I just added Firebase.
Since 4 days I am trying to make it work, and yesterday finally I started seeing events coming in DebugView (which proves that I configured it correctly). It was moment of pure joy, as each single event was recorded in DebugView (no matter how many times I clicked a button -> all events reached Firebase).
This happiness didn't last long however.
Today it stopped work, but not like "never works", but it skips like 95-99% of events (some events sometimes gets to DebugView. Wow! Pure magic.
Using logcat, I can see all events are successfully uploaded/sent.
I wonder if there is any undocumented "magical" thing that might me blocking my events?
Or is Firebase down today (21st Sept 2022)?
Please note that:
When my events passes - it shows "1" in USERS IN LAST 30 MINUTES which is correct.
When events are not reaching DebugView, then nothing is shown in USERS IN LAST 30 MINUTES (which basically means that it is not only problem with DebugView - but actually no activity is reaching Firebase AT ALL).
Following picture proves that some events reached Firebase (but dozens other events, like screen_view or my custom dummy_event never got there).
Last picture proves that my events actually are successfully sent.
EDIT 25th Sept 2022
I deleted Firebase project and created a new one, run flutterfire configure and guess what? It started to work WITHOUT any other change in the code. (please note that I was running flutterfire configure many time for previous firebase project as well, without any result).
I am frustrated that I wasted few hours on looking for a bug in my code, while it was some "magic" on Firebase side that simply made it NOT WORKING.
So do you think it is over now? And that everything works?
You can't be farther from truth.
This image shows that there was 1 active user. Yes, it was me debugging app using DEBUG build. So since it was working, and decided to make final release build to my device (flutter run --release) and guess what?
Yeap - nothing shows in Firebase again. Simply my release build, installed on my device does not shows any activity on Firebase.
Is it because it was not downloaded from Google Play?
Is it because I have some misconfiguration?
Is it because Firebase has bug?
Who knows... Firebase is like Hogwart - full of magic.
I have a personal expenses app in which I have a Week model which holds user expanses over week and at the end of the week uploads it in cloud. My problem is that how can I implement a situation in which Week model is created at first day of week(eg.saturday) periodically even if the app is not running??? Is that even possible??
I searched a little and saw
timer.periodic(duration,callback);
but I don't think that would work in background
Maybe this will help you:
Firstly
You have to use Timer from dart:async to run periodically method, and put the duration for 7 days.
Timer.periodic(
Duration(days: 7),
(timer){
// Create new week model in database.
}
);
Secondly
Use workmanager to run the previous code in the background, it will executed weekly.
You can use background_fetch plugin. But this plugin's lack of it is that works stable on just Android. You need to read the official document.
I'm using GitHub API v3 to connect to a repository and get the list of issues that were update/created since a specific date. I use these parameters to get a filtered result:
filter: all
labels: bug
state: all
sort: updated
direction: ascendent
since: date
If i find any result, for each issue I get the issue events that triggered a change (filtering for the ones that happened since date).
Everything works fine for every issue event except for locked and unlocked
events that, for some reason, don't update the issue updated field.
This leads to the inability to get then the list of issues that were updated since that specific date and therefore I don't check for the issue events.
Questions:
Is there a reason why these two events don't update the issue?
Is there an acceptable solution, except for the one where I should get all the issues and query them manually?
As of today (4th of October, 2015), I cannot reproduce this issue. If it was reproducible when the question was posted, probably it was a bug, not a feature.
Is there a reason why these two events don't update the issue?
They do update the issue (see the updated_at field) and the since parameter works fine.
Is there an acceptable solution, except for the one where I should get all the issues and query them manually?
Just use the since parameter, the way how it is supposed to work, but keep in mind the timezone could be different. Since you're in Romania (like me! :-)) and your server could be into another timezone, you may want to modify the date to match the Romanian time. That's most probably your issue. Just add/substract few hours and see if that helps.
curling the issues, I cannot reproduce the behavior you have.
On the other side, you may want to use the locked parameter which is anyway updated.
I just came across a bug in my program, that has me confused. I add several events to the iPhone calendar in my app. I found that when I receive a "No end date has been set." error when calling saveEvent:span:error:, all subsequent calls to saveEvent:span:error: result in the same error message. If I change the culprit object to be valid, all events save successfully. Has anybody ran into this? Or do you know why one error might cause all future calls to result in the same error?
I know that I just need to not save an event with no end date set to fix this, but I would like to know why this is happening.
Thanks.
I figured this out. There is a bug in the EKEvent SDK on iOS 5 that is causing this. Hopefully it will be fixed in the first update to iOS 5.
Solution:startDate and endDate should be different.
[event setStartDate:date];
[event setEndDate:[date dateByAddingTimeInterval:1.0]];
I am making a simple time sheet for which people can register times
worked on a bug real quickly.
But the hours added to the bugs_activity table are not noticed
anywhere.
here is a simple made up line
Bugzilla::Bug::LogActivityEntry(1, 'work_time', 0, 66, 1, '2010-01-12 14:44:44');
Pretty much, add 66 hours to bug 1, work time. This executes like I would expect but does nothing else. I also need to send e-mails and add comments. I can't find anything on using Bug.pm or LogActivityEntry API.
Is this a huge undertaking or what ?
What I would need is what else is required of me, this is just a batch job that runs when the user presses submit and this info can be on many bugs. I know how to get the bugs, user and such, just not registering the hours, I need the final item. This can be almost as rough as the example above.
I am using Bugzilla 3.4.4
Time worked is kept in longdescs table - the table with comments. Hours worked in fact is a property of a comment. (I also think it's weird.)
bugs_activity table that you're modifying is the table for the history of changes, I bet you can see the result of your call on the "bug activity" page. But it does not change the state of the bug.
Hope this helps.
Igor