search

Bridgeconn / VachanAppReact

Companion App to https://vachanonline.com
https://play.google.com/store/apps/details?id=com.bridgeconn.vachango
MIT License
2 stars 3 forks source link

Changing contact email in VachanGo #283

Open VineethaVi opened 1 year ago

VineethaVi commented 1 year ago

change the contact email to brigdeconn.com email MicrosoftTeams-image

AnnCherianA commented 1 year ago

@VineethaVi this issue was already created ,tested in apk1.3.6-alpha.3 and moved to Done issue #256 https://github.com/Bridgeconn/VachanAppReact/issues/256 @VineethaVi please check how this problem happened again

VineethaVi commented 1 year ago

Earlier release notes was inside 'About us' . After fixed the issue https://github.com/Bridgeconn/VachanAppReact/issues/256 , release notes kept in separate tab. The content by mistake copied from coda instead of the updated content. That is how the email got replaced. Now the coda has been updated.

VineethaVi commented 8 months ago

As Seema updated in the QA stand up , emails are not coming to bridgeconn.com . In Vachango App, does not show the email for contact, but in the playstore it shows the bridgeconn.com email.

Adding the screenshot

MicrosoftTeams-image (108)

AnnCherianA commented 8 months ago

Earlier release notes was inside 'About us' . After fixed the issue #256 , release notes kept in separate tab. The content by mistake copied from coda instead of the updated content. That is how the email got replaced. Now the coda has been updated.

Vineetha as you said if the is issue was fixed on Jun 28, then the issue is not supposed to be in New. The issue did not get moved to the right pipeline.

VineethaVi commented 8 months ago

Earlier release notes was inside 'About us' . After fixed the issue #256 , release notes kept in separate tab. The content by mistake copied from coda instead of the updated content. That is how the email got replaced. Now the coda has been updated.

Vineetha as you said if the is issue was fixed on Jun 28, then the issue is not supposed to be in New. The issue did not get moved to the right pipeline.

Forgot to update the issue after fixing

VineethaVi commented 8 months ago

This issue was fixed . so, closing this issue.

AnnCherianA commented 8 months ago

@VineethaVi please add the correct label.