Agenda loadItemsForMonth calls two time and gives wrong date

[ManishAhire]

Description

Following are the issues in my app :-

1. First time loadItemsForMonth calls twice.
2. On scroll month loadItemsForMonth gives wrong date.
3. On press date, loadItemsForMonth method call.

Expected Behavior

1. First time loadItemsForMonth call only one time and it should return the exact date.
2. On scroll month loadItemsForMonth return exact the date of visible month.
3. On press date, calls only onDayPress not loadItemsForMonth.

My Code

<Agenda
        items={this.state.items}
        loadItemsForMonth={day => this.loadMonthData(day)}
        onDayPress={day => this.onDatePress(day)}
        renderItem={this.renderItem.bind(this)}
        renderEmptyDate={this.renderEmptyDate.bind(this)}
        rowHasChanged={this.rowHasChanged.bind(this)}
        refreshing={false}
        
/>

loadMonthData(day) {
    console.log("Month date :- ", day);
}

onDatePress(day) {
    console.log("On date press :- ", day);
}

[jhonatansaman]

any solution?

[dophlin]

+1

[elisson]

+1 any solution?

[foxfl]

+1

[Plaoo]

+1

[fthkrtl]

same issue

[ConnectedReasoning]

Happens to me too. Exactly as described It seems to skip back exactly 60 days

[GladeyMs]

+1

[MrFaisal100]

did anyone manage to solve this?

[lironsher]

+1

[onisaint]

+1

[kalebjdavenport]

Same issue.

[kalebjdavenport]

So...I tried to debug the error myself. I don't like messing in module code for risk it will break on updates, and I don't understand the issue well enough to send a pull request, but when I add the prop

onVisibleMonthsChange={months => {
       console.log('now these months are visible', months);
}}

it shows that an additional month is being added the the "months" array. Then the onViewableItemsChanged is being called for some reason and setting the component state to months[0]. I changed the function to select months[1] and it appears to work well enough for now. I don't know why this is happening, but if someone on the core team is going to fix the issue, I hope this will be a lead!

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[rojeda24]

Any solution??

[FadiAboMsalam]

Any solution to this ?

[Arslan106]

still no solution?

[meliodev]

Yep same issue for me

[hnrazevedo]

Any news on the case?

[ViniciusGularte]

same problem here, any news?

[wilav-dev]

Same here!

[johnpanos]

Also same here...

[nickdalts]

Same!

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[JosiasBatista]

I have the same problem here!

[merouan95]

Same !

[albionaberisha]

I have the same problem!

[ekrebs]

Another month, another person with this issue. How has everyone else worked around this?

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[insidewill]

Anyone?