gmobilesync Work Item Rss Feed

Created Issue: Difference at date time on Google Calendar and Pocket PC. [14104]

Psymon — Thu, 10 Sep 2009 11:38:24 GMT

Hello!!!

I am using the 1.3.5.34682 version of GMobileSync and i am having a little trouble.
The date time at Google Calendar is 2 hours later than the date time at pocket pc (WM5). I checked both time zones and are the same (Madrid,Paris GMT+1).

Thank you for the develop of this application.

Regards.

Commented Issue: Resets Delete G. Calendar Items

lifanxi — Sat, 15 Aug 2009 16:53:11 GMT

When I go through a reset on my mobile device, all my calendar entries disappear. I tried to restore them oiwht GMobileSync, but it went ahead and uploaded the "deletions" to Google Calendar. I lost all my calendar data. Is there a way for the program to only be set to do a 1-way sync at times?
Comments: ** Comment from web user: lifanxi **

I do feel sorry for this inconvenience the software brought you.
The events should not be cleared on Google Calendar just because you reset (hard reset) your phone. If you hard reset your phone and reinstall GMobileSync it should read all the Google Calendar data and save it into Pocket Outlook.
One possible reason is that you have reset your phone and you didn't reinstall GMobileSync (maybe because it has been installed on the Storage Card), then the problem will happen. Because GMobileSync thinks that you have deleted all the appointments in Pocket Outlook, thus the related items on Google Calendar should also be cleared.
I do want to make GMobileSync better, however, currently I don't have enough time to pay on this project, so I cannot commit when I will fix these issues. If some people would like to continue this project, please let me or superic know.
Meanwhile, Google Sync service may be a better choice for Google Calendar sync.

Commented Issue: Resets Delete G. Calendar Items

Carlos_rpg — Sat, 15 Aug 2009 05:21:06 GMT

a First Sync Feature seams to be necessary to solve this issue...

Commented Issue: Error: Cannot add a recipient with an empty or null name to a recipient collection.

Noe — Mon, 03 Aug 2009 08:27:15 GMT

I'm having the same issue that others are reporting. Phone is a Sprint HTC touch, gmobilesync version is 1.3.5.34682.

Error: Cannot add a recipient with an empty or null name to a recipient collection.

As with the other report, the error comes up on the seventh item of 37 during the sync process then shuts down the sync.
Comments: ** Comment from web user: Noe **

I have also the same problem with a PU10 from Qtek and Win Mobile 06 (OS 5.2.1708), is there a solution to bypass this error ?

Created Issue: Accepted/declined appts are being UNaccepted by the sync

selosmini — Sat, 11 Jul 2009 15:30:55 GMT

When I am invited to appts, I will accept or decline them on Google Calendar. But when I sync my phone to gCal, the sync UNaccepts/ UNdeclines them. I have to go back into gCal and accept or decline them again each time I sync my phone. How do I prevent this from happening. Am I handling it incorrectly?

Commented Feature: Setting reminders on Windows Mobile

selosmini — Tue, 07 Jul 2009 18:38:04 GMT

GMobileSync creates the events on the mobile device with reminder even though i've set no reminder on Google Calendar.

IMHO the popup reminder on google should be reflected as reminder on the mobile device, the other reminders shouldn't.
Comments: ** Comment from web user: selosmini **

I agree with this comment. Because Gcal allows users to set up default auto reminders that can go to mobile (or email, etc), the auto reminder set on the mobile calendar is unneeded- and a lot of times annoying.

Commented Issue: Native method call failed -- error

lifanxi — Wed, 25 Mar 2009 02:38:22 GMT

After the sync initiates (the download barometer actually starts), the process errors out:

"Info
Please report this error: Native method call failed."

Since last sync I have installed Cingular Xpress Mail on my phone (Samsung Blackjack) in order to access a corporate Lotus Notes account for email and calendar. I am wondering if there is now a conflict of some sort.

thanks
Mary
Comments: ** Comment from web user: lifanxi **

I am able to reproduce the problem like this:

Use program to generate an appointment like this:

Appointment app = new Appointment();
app.AllDayEvent = true;
app.BusyStatus = BusyStatus.Free;
app.RecurrencePattern.PatternStartDate = somedate;
app.RecurrencePattern.RecurrenceType = RecurrenceType.Yearly;
app.RecurrencePattern.DayOfMonth = somedate.Day;
app.RecurrencePattern.NoEndDate = true;
app.ReminderSet = false;
app.Start = somedate;
app.Subject = the_subject;
session.Appointments.Items.Add(app);

Then you will get a appointment that cannot be saved correctly in Pocket Outlook, it seems that this has some relation to the fact that appointment does not have a valid End date. When such appointments exists in Pocket Outlook, GMobileSync will report "Native Method Call Failed" when uploading local changes to GCal.

Currently, I have used a workaround to solve the problem. The workaround is set the "Start" and "End" to the appointment before Update() the appointment. I works fine in my test environment. It will be greatly appreciated if somebody here can help to test this.

I have released a development build for this issue, available at
http://gmobilesync.codeplex.com/Release/ProjectReleases.aspx?ReleaseId=25180

The revision number for this build should be >= 32483.

Commented Issue: Error: Cannot add a recipient with an empty or null name to a recipient collection.

horace_condition — Fri, 20 Mar 2009 13:21:01 GMT

Same issue on htc Diamond with 1.3.7 version.
I beg it's crashing on recurring appointments. I'll test it.

Commented Issue: NullReferenceException

chillrobot — Wed, 11 Mar 2009 07:49:38 GMT

Hi aLL, I had this issue.

When i Sync my HTC touch with Gmobile i had this Error Message " NullReferenceException"

But if i change it to:
Syn Previous Days 7
Sync Future Days 7
There is no error. BUT the Calendar DID NOT update on both Gmail and HTC.

The error will appear when i set to Sync more than 14 days( Future ).

Version 1.3.5.34682
HTC Touch ( CE OS 5.2.1238 (build 17745.0.2.3 )

Can anyone advice please ......... THANKS !!
Comments: ** Comment from web user: chillrobot **

My first experience with GMobileSync is with the 1.3.7 beta, and I encountered this exception. I'm using an HTC Tytn with WM5.

Some events from my Google calendars made it to my mobile, and many events from my mobile calendar made it to my Google default calendar. It's not clear if this exception was event-specific.

Commented Issue: Native method call failed -- error

lifanxi — Fri, 27 Feb 2009 02:45:46 GMT

I'm still working on this. But unfortunately, I am busy these days and the progress is slow.

It has been confirmed that the problem happens when updating a local appointment. I plan to modify the source code and let GMobileSync skip all these items. The code change is not small, so I need more time. The ETA is before next Monday.

The reason why updating local appointments causes exceptions is still unknown, it seems to be some problem of the Outlook itself.

Currently, I am not sure if all the updates on appointments will cause exceptions, if so, skipping all the appointments that causes exceptions will be a bad idea, becuase it will make this software totally useless :( But as far as I'm concerned, there's not better choice at this moment.

Commented Issue: Native method call failed -- error

GeraldS — Thu, 26 Feb 2009 17:44:40 GMT

anything new regarding this issue?

Commented Issue: Native method call failed -- error

lifanxi — Fri, 20 Feb 2009 11:54:08 GMT

Thanks GeraldS. Much useful information you have provided.

From your description, it seems that it has little relation to the memory issue.

I made a new debug build (Attached as debug0220_log.zip), this debug build has the ability to output process log. Would you try again and send me the log files? Just unzipped the file and replace the GMobileSync.exe in \ProgramFile\GMobileSync, after you run the problem, a debug log file will be created as \GMSLog.txt. If it is not there, check \ProgramFile\GMobileSync folder. After you have reproduce the problem (when the program said the Native method call failed, please retry 3 times), use Options->Exit to close the program and get the \GMSLog.txt file, attach the log file here or send it to gmobilesync <at> freemindworld.com

Thank your for your support. Your help are greatly appreciated.

Commented Issue: Native method call failed -- error

GeraldS — Fri, 20 Feb 2009 08:28:00 GMT

okay, some stats prior to running gmobilesync:
free data memory: 11.70 MB
free program memory: 27.77 MB
ram size: 128MB
flash size: 256 MB
(not sure if the english terms are correct, my windows is german, i'm translating on the fly)
the device is a HTC Polaris (Touch Cruise)
gmobilesync is the only application running.

stats at the "call failed"-point:
same free memory as before. Do i look at the right spot for free memory? It says 71% memory used, after closing gmobilesync it's 70%.

I retried 5 times now, but to no avail.

I set the syncing timespan to the last 7 days and the next 60 days, but that doesn't seem to matter, I got the same with the next 30 days.
There are 37 local updates (according to gmobilesync).
There are about 20 events in 4 calendars on google calendar for the next 60 days.

Not sure if it's relevant, but anyway:
Most "local update" entries are birthdays, yearly recurring full day events. Not a single one of them showed up on my google calendar.
I renamed my default calendar on google, might that be an issue?

Commented Issue: Native method call failed -- error

lifanxi — Fri, 20 Feb 2009 06:11:15 GMT

I have made another debug build (attached as debug0220.zip), would you please have a try? Unzip it and put the GMobileSync.exe in \Program File\GMobileSync, overwrite the old one.

Currently, I am still not able to reproduce the problem locally. From the information get from the Internet, I am wondering if this problem is related to memory issues. If there is not enough memory on a Windows mobile system, the system may close some of the programs which it thinks is not active. If the system close the Pocket Outlook session, it may lead to some problems.

In this debug build, I have changed following:

- Create Outlook Session only when we are going to need it. It other build, the Outlook Session is created immediately when the program starts.
- If the Native Method Call exception occurred during synchronize local changes to GCal, pop up a dialog box to ask if user want a retry, if you say "Yes", it will create a new Outlook Session object and retry operation.

I suggest to do the following test:

If the "Native Method Call failed" dialog box show up, choose "Yes" to retry (may be several times). Please pay attention if there is any chance the sync process can finish correctly.

Since I am wondering if this problem has some relation to memory issue. I'd like to know the following information:

- The memory size of your phone
- How many events have been get from GCal to local. (Approximate number is OK)
- How many appointments are there in Pocket Outlook. (Approximate number is OK)

Commented Issue: Native method call failed -- error

GeraldS — Thu, 19 Feb 2009 13:04:31 GMT

Latest message before the error is "Found N local updates...".
The new .exe gives the same error as before.
Using the additional .dlls doesn't solve it either.

I'll happily volunteer for further testing.

Commented Issue: Native method call failed -- error

lifanxi — Thu, 19 Feb 2009 05:47:56 GMT

The dll.zip file mentioned in last comment.

Commented Issue: Native method call failed -- error

lifanxi — Thu, 19 Feb 2009 05:47:02 GMT

I was not able to find more useful information on Internet about this problem.

I'd like to confirm the following problem:

1. When does this error message pop up? Does it come out after clicked "Sync" and when screen is showing "Saving ? of ? events".
2. Is there any relation to the type of sync operations? Does it happen every time or only when updating/creating/deleting events.

I have made a debug module, is there any body can help to test? First download the GMobileSync.zip file and unzip it, replace the \Program Files\GMobileSync\GMobileSync.exe with the file in this package and try again. If it doesn't solve the problem, download the "dll.zip" file and unzip it, copy the three .dll file to \Program Files\GMobileSync\ and try again.

It will be greatly appreciated if any one who suffers this problem can help to test the debug module.

Commented Issue: Setting reminders on Windows Mobile

lifanxi — Thu, 19 Feb 2009 03:51:21 GMT

This is not bug, GMobileSync has been designed to act like this since it was born.

So I change the Type of this issue to "Feature", which I will consider to solve it in future releases.

Commented Issue: Error "execution of request" New events from handheld not being synced

lifanxi — Thu, 19 Feb 2009 03:47:02 GMT

Whenever I sync it downloads the calendars, adds new events from google cal to handheld cal. It then fiunds the local changes and subsequently gives me this error.
Execution of request failed: http://www.google.com/calendar/feeds/default/private/full

The end result is that I'm getting one way synchronization. Google to handheld but not handheld to google.

V 1.3.7 - not using a proxy, WM 5 on an iPaq
Comments: ** Comment from web user: lifanxi **

It seems to be similar to Issue 12630. But actually they are different. Issue 12630 only happens on new appointments created locally. And this seems only happen when the local appointments get changed.

So I need more information for this case:

1. Have you used any old version of GMobileSync?
2. Is this "local change" belong to "Update", which means you have locally modified the appointment and this appointment is originally synced from GCal.
3. Is this always reproducible?
4. If you have used any old version of GMobileSync, suggest to perform a "Option->Delete Event" and sync again to see if the problem still exists.

Commented Issue: Native method call failed -- error

lifanxi — Thu, 19 Feb 2009 03:36:18 GMT

Seems that this problem has been reported many times.

I have never reproduced this problem locally. After I search the Internet, I found some clues that it may lead to multiple instance of POutlook and error usage of the Outlook object. I'm confirming this and will update if there's any new findings.