Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

map not loading when online #26998

Merged

Conversation

pradeepmdk
Copy link
Contributor

@pradeepmdk pradeepmdk commented Sep 8, 2023

Details

Fixed Issues

$ #26589
PROPOSAL: #26589

Tests

  1. Make sure to log out.
  2. Refresh the page (for browser) or reopen the app (for native/desktop app).
  3. Log in with any account.
  4. Make sure device offline.
  5. Click plus button and then select Distance Request.
  6. Switch the device back online.
  7. Verify the map displays properly.
  • Verify that no errors appear in the JS console

Offline tests

QA Steps

  1. Make sure to log out.
  2. Refresh the page (for browser) or reopen the app (for native/desktop app).
  3. Log in with any account.
  4. Make sure device offline.
  5. Click plus button and then select Distance Request.
  6. Switch the device back online.
  7. Verify the map displays properly.
  • Verify that no errors appear in the JS console

PR Author Checklist

  • I linked the correct issue in the ### Fixed Issues section above
  • I wrote clear testing steps that cover the changes made in this PR
    • I added steps for local testing in the Tests section
    • I added steps for the expected offline behavior in the Offline steps section
    • I added steps for Staging and/or Production testing in the QA steps section
    • I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
    • I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
    • I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).
  • I included screenshots or videos for tests on all platforms
  • I ran the tests on all platforms & verified they passed on:
    • Android / native
    • Android / Chrome
    • iOS / native
    • iOS / Safari
    • MacOS / Chrome / Safari
    • MacOS / Desktop
  • I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
  • I followed proper code patterns (see Reviewing the code)
    • I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
    • I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
    • I verified that comments were added to code that is not self explanatory
    • I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
    • I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method
      • If any non-english text was added/modified, I verified the translation was requested/reviewed in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:
    • I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
    • I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is approved by marketing by adding the Waiting for Copy label for a copy review on the original GH to get the correct copy.
    • I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
    • I verified the JSDocs style guidelines (in STYLE.md) were followed
  • If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
  • I followed the guidelines as stated in the Review Guidelines
  • I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
  • I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
  • I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
  • I verified that if a function's arguments changed that all usages have also been updated correctly
  • If a new component is created I verified that:
    • A similar component doesn't exist in the codebase
    • All props are defined accurately and each prop has a /** comment above it */
    • The file is named correctly
    • The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
    • The only data being stored in the state is data necessary for rendering and nothing else
    • If we are not using the full Onyx data that we loaded, I've added the proper selector in order to ensure the component only re-renders when the data it is using changes
    • For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
    • Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
    • All JSX used for rendering exists in the render method
    • The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions
  • If any new file was added I verified that:
    • The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory
  • If a new CSS style is added I verified that:
    • A similar style doesn't already exist
    • The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(themeColors.componentBG))
  • If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
  • If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
  • If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
  • If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
  • If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
  • If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
  • I have checked off every checkbox in the PR author checklist, including those that don't apply to this PR.

Screenshots/Videos

Web
Screen.Recording.2023-09-08.at.6.51.39.AM.mov
Mobile Web - Chrome
Record_2023-09-08-07-28-28.mp4
Mobile Web - Safari
WhatsApp.Video.2023-09-08.at.7.15.05.AM.mp4
Desktop
Untitled.mov
iOS
WhatsApp.Video.2023-09-08.at.9.03.26.AM.mp4
Android
Record_2023-09-08-07-52-26.mp4

@pradeepmdk pradeepmdk requested a review from a team as a code owner September 8, 2023 01:24
@melvin-bot melvin-bot bot requested review from ntdiary and removed request for a team September 8, 2023 01:24
@melvin-bot
Copy link

melvin-bot bot commented Sep 8, 2023

@ntdiary Please copy/paste the Reviewer Checklist from here into a new comment on this PR and complete it. If you have the K2 extension, you can simply click: [this button]

@pradeepmdk pradeepmdk marked this pull request as draft September 8, 2023 01:24
@pradeepmdk pradeepmdk marked this pull request as ready for review September 8, 2023 03:35
@@ -3,6 +3,10 @@ import {AppRegistry} from 'react-native';
// This is a polyfill for InternetExplorer to support the modern KeyboardEvent.key and KeyboardEvent.code instead of KeyboardEvent.keyCode
import 'shim-keyboard-event-key';

// load all chunk file map when online
import 'react-map-gl';
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We don't have to do it here, should have a better way to load it. : )

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@ntdiary do you have any suggestion here where we need load. when I am checking https://github.com/Expensify/App/blob/d89ca7043b9bc923c0599836a3571bb15d40ed7c/src/components/MapView/MapView.web.tsx#L8C36-L8C48 loading this but when we open distance page at the time only components mounted so it's loading all necessary chunk file when offline this is ignored.

Note: This will be needed only for the web and desktop. so I added on the platform setup this will call initially and load all chunk files. like shim-keyboard-event-key

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@ntdiary could you check this

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I understand your point, but we already have MapView.web.tsx, we can also do it this way (available on both web and desktop):

diff --git a/src/components/MapView/MapView.web.tsx b/src/components/MapView/MapView.web.tsx
--- a/src/components/MapView/MapView.web.tsx	(revision f896f71a1ce00320a2ba029e44396d4e29b88223)
+++ b/src/components/MapView/MapView.web.tsx	(date 1694452383426)
@@ -14,6 +14,7 @@
 import Direction from './Direction';
 import {MapViewHandle, MapViewProps} from './MapViewTypes';
 
+import MapboxGl from 'mapbox-gl';
 import 'mapbox-gl/dist/mapbox-gl.css';
 
 const MapView = forwardRef<MapViewHandle, MapViewProps>(
@@ -65,6 +66,7 @@
                 {...responder.panHandlers}
             >
                 <Map
+                    mapLib={MapboxGl}
                     ref={setRef}
                     mapboxAccessToken={accessToken}
                     initialViewState={{

I'm not too sure if import() is allowed, if so, we can also do it this way:

diff --git a/src/components/MapView/MapView.web.tsx b/src/components/MapView/MapView.web.tsx
--- a/src/components/MapView/MapView.web.tsx	(revision f896f71a1ce00320a2ba029e44396d4e29b88223)
+++ b/src/components/MapView/MapView.web.tsx	(date 1694452383426)
@@ -65,6 +65,7 @@
                 {...responder.panHandlers}
             >
                 <Map
+                    mapLib={import('mapbox-gl')}
                     ref={setRef}
                     mapboxAccessToken={accessToken}
                     initialViewState={{

Additionally, let's wait for @hayata-suenaga's opinion to see if we should continue with this PR. 🙂

Copy link
Contributor Author

@pradeepmdk pradeepmdk Sep 11, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@ntdiary MapView.web.tsx already we have the import statement. the actual problem is MapView.web.tsx will trigger (mount) only when you open a distance request page like a token api trigger. before open up the distance request page your offline means map file(chunk) is not loading.

Copy link
Contributor

@ntdiary ntdiary Sep 12, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@pradeepmdk, in the first approach, mapbox-gl will also be bundled into the vendors-xxx.js (instead of being a separate js file), so subsequently it can be safely loaded. In the second approach, because there is a preceding isOffline condition, mapbox-gl can also be safely loaded when the device comes back online. If you find it hard to believe, please test it out first, and feel free to let me know if you have any other questions.

{!isOffline && Boolean(mapboxAccessToken.token) ? (

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@ntdiary this is working mapLib={import('mapbox-gl')} let me update PR

@hayata-suenaga
Copy link
Contributor

hi @ntdiary @pradeepmdk

I'm sorry I'm juggling several issues in addition to a different project

could you tell me what chunk files are and why we need to touch file import statements in this PR?

@pradeepmdk
Copy link
Contributor Author

hi @ntdiary @pradeepmdk

I'm sorry I'm juggling several issues in addition to a different project

could you tell me what chunk files are and why we need to touch file import statements in this PR?

Untitled.mov

@hayata-suenaga when offline the first time opening the distance request and after that when try open multiple times map doesn't load.

@ntdiary
Copy link
Contributor

ntdiary commented Sep 12, 2023

could you tell me what chunk files are and why we need to touch file import statements in this PR?


image
@hayata-suenaga, our Map component comes from the react-map-gl package, it uses the const mapLib = import('mapbox-gl'); dynamic import statement to load the mapbox-gl package.
This causes the mapbox-gl package to be built as a separate js file (i.e. 158-70d9a0576645807b49ed.bundle.js), and the above code only executes once.
So once the distance request page is first opened when the device is offline, this js file will fail to load properly, then afterwards even if the device comes back online the Map component will be unable to render (because mapLib promise is already in a rejected state).

To solve this problem, we either need to bundle the mapbox-gl package into the vendors-xxx.js file, or we need to dynamically load mapbox-gl in MapView.web.tsx using import().

mapbox-gl-trunk.mp4

@hayata-suenaga
Copy link
Contributor

@ntdiary

thank you so much for the explanation. could you explain more about these two options?

we either need to bundle the mapbox-gl package into the vendors-xxx.js file, or we need to dynamically load mapbox-gl in MapView.web.tsx using import().

@ntdiary
Copy link
Contributor

ntdiary commented Sep 12, 2023

thank you so much for the explanation. could you explain more about these two options?

@hayata-suenaga, it's my pleasure. react-map-gl provides us with the mapLib prop:

bundle the mapbox-gl package into the vendors-xxx.js file

This approach is module (or static) import, mapbox-gl is embedded into the main vendors-xxx.js bundle.
As long as the app is loaded normally when the device is online, we don't have to worry about mapbox-gl not being found afterwards.

diff --git a/src/components/MapView/MapView.web.tsx b/src/components/MapView/MapView.web.tsx
 import Map, {MapRef, Marker} from 'react-map-gl';
+import MapboxGl from 'mapbox-gl';

 import responder from './responder';
 import utils from './utils';
@@ -65,6 +66,7 @@ const MapView = forwardRef<MapViewHandle, MapViewProps>(
                 {...responder.panHandlers}
             >
                 <Map
+                    mapLib={MapboxGl}
                     ref={setRef}
                     mapboxAccessToken={accessToken}
module-import.mp4

dynamically load mapbox-gl in MapView.web.tsx using import()

This approach is dynamic import (will still enable bundle splitting).
Because it's executed at runtime, the Map component will attempt to import it (and cache it, so no need to worry about duplicate import) when the device is online.

diff --git a/src/components/MapView/MapView.web.tsx b/src/components/MapView/MapView.web.tsx
@@ -65,6 +65,7 @@ const MapView = forwardRef<MapViewHandle, MapViewProps>(
                 {...responder.panHandlers}
             >
                 <Map
+                    mapLib={import('mapbox-gl')}
                     ref={setRef}
                     mapboxAccessToken={accessToken}
                     initialViewState={{
dynamic-import.mp4

@hayata-suenaga
Copy link
Contributor

ah I see that made thing more clear

@ntdiary which do you think is the best option? I think dynamic import seems better to me?

@ntdiary
Copy link
Contributor

ntdiary commented Sep 12, 2023

@hayata-suenaga , eh, Besides the dynamic import has an error log for the first offline load, I didn't see other obvious differences between the two approaches, so in my opinion both are good. Also, we haven't used dynamic import in our project yet, if allowed, we can try using it first. : )

@pradeepmdk
Copy link
Contributor Author

@ntdiary @hayata-suenaga dynamic import is working fine in our project. I already updated the PR

@hayata-suenaga
Copy link
Contributor

Besides the dynamic import has an error log for the first offline load

Is there a way to suppress the error log? why do we get the error log? (sorry for asking a lot of questions)

Also, we haven't used dynamic import in our project yet

I thought we're using dynamic imports in some of the screens (we only load/fetch components code when navigated to them?)

@ntdiary
Copy link
Contributor

ntdiary commented Sep 13, 2023

Is there a way to suppress the error log? why do we get the error log? (sorry for asking a lot of questions)

@hayata-suenaga, using module import can avoid this error log. If using dynamic import, there may be no way around it. This error still comes from the following line of code. When we open the distance request page, browser will load react-map-gl, and then this line of code will execute and request the mapbox-gl.js(separate file). But because the device is offline, it will print a ERR_INTERNET_DISCONNECTED error log.

By the way, don't worry, I think having a clear and comprehensive understanding is more helpful for the quality of our project. 🙂


I thought we're using dynamic imports in some of the screens (we only load/fetch components code when navigated to them?)

image

component load and dynamic import(i.e. import('package') statement) we are talking about here are slightly different.
As shown in the image above, the components of our app are all bundled in main-xxx.js, and the packages under node_modules are almost all in vendors-xxxx.js. (i.e., they all use module import).
Their formats can be simplified to:

{
  './src/pages/iou/DistanceRequestPage.js': () => {
    eval('<DistanceRequestPage xxx />');
  },
}

For example, when we open the distance request page, browser will find the function corresponding to ./src/pages/iou/DistanceRequestPage.js and load its content (in main-xxx.js, it won't request a separate DistanceRequestPage.js file).

@pradeepmdk
Copy link
Contributor Author

@hayata-suenaga bump

@hayata-suenaga
Copy link
Contributor

ah I thought that separate files are fetched with module imports. Let's go with module import approach

@pradeepmdk sorry for the late response 🙇

@pradeepmdk
Copy link
Contributor Author

@hayata-suenaga np. update now to module import @ntdiary

@ntdiary
Copy link
Contributor

ntdiary commented Sep 18, 2023

@pradeepmdk, There are two pending tasks need to be addressed, feel free to let me know if there are any problems. : )
image

@pradeepmdk pradeepmdk force-pushed the fix/26589-map-route-is-not-genrated branch from 5534443 to 195b191 Compare September 18, 2023 17:01
@pradeepmdk
Copy link
Contributor Author

pradeepmdk commented Sep 18, 2023

@pradeepmdk, There are two pending tasks need to be addressed, feel free to let me know if there are any problems. : )

sorry @ntdiary i am not able to see this in review comments so that missed this. i am updated now..
let me know if you want ignore this line here
const doesRouteExist = !lodashIsNull(lodashGet(transaction, 'routes.route0.geometry.coordinates'));
i will remove it. still that PR not yet merged.

@ntdiary
Copy link
Contributor

ntdiary commented Sep 18, 2023

i will remove it. still that PR not yet merged.

Yeah, they have confirmed they will fix that case, so we can focus on our own scenario here.

@pradeepmdk
Copy link
Contributor Author

@ntdiary updated.

@ntdiary
Copy link
Contributor

ntdiary commented Sep 19, 2023

@pradeepmdk, great! Could you please explain this? And we are very close to the end. 😄
image

@pradeepmdk
Copy link
Contributor Author

pradeepmdk commented Sep 19, 2023

@pradeepmdk, great! Could you please explain this? And we are very close to the end. 😄 image

yes i agree we don't need when i am testing i removed the token from indexdb manually deleted so callback its not triggering so that i added this one.
Thanks for finding this one.

@ntdiary one small doubt how you are adding this review comment because i am not able see this here.🤔

and stop functions changes already fixed by some other PR so merged with main

@pradeepmdk pradeepmdk force-pushed the fix/26589-map-route-is-not-genrated branch from 7282837 to 5b7f27e Compare September 19, 2023 03:12
@ntdiary
Copy link
Contributor

ntdiary commented Sep 19, 2023

@ntdiary one small doubt how you are adding this review comment because i am not able see this here.🤔

@pradeepmdk, ah, my bad, I forgot to submit the review, and will start testing later. 😂

@ntdiary
Copy link
Contributor

ntdiary commented Sep 19, 2023

Reviewer Checklist

  • I have verified the author checklist is complete (all boxes are checked off).
  • I verified the correct issue is linked in the ### Fixed Issues section above
  • I verified testing steps are clear and they cover the changes made in this PR
    • I verified the steps for local testing are in the Tests section
    • I verified the steps for Staging and/or Production testing are in the QA steps section
    • I verified the steps cover any possible failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
    • I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
  • I checked that screenshots or videos are included for tests on all platforms
  • I included screenshots or videos for tests on all platforms
  • I verified tests pass on all platforms & I tested again on:
    • Android / native
    • Android / Chrome
    • iOS / native
    • iOS / Safari
    • MacOS / Chrome / Safari
    • MacOS / Desktop
  • If there are any errors in the console that are unrelated to this PR, I either fixed them (preferred) or linked to where I reported them in Slack
  • I verified proper code patterns were followed (see Reviewing the code)
    • I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick).
    • I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
    • I verified that comments were added to code that is not self explanatory
    • I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
    • I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method
    • I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
    • I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is approved by marketing by adding the Waiting for Copy label for a copy review on the original GH to get the correct copy.
    • I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
    • I verified the JSDocs style guidelines (in STYLE.md) were followed
  • If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
  • I verified that this PR follows the guidelines as stated in the Review Guidelines
  • I verified other components that can be impacted by these changes have been tested, and I retested again (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar have been tested & I retested again)
  • I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
  • I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
  • If a new component is created I verified that:
    • A similar component doesn't exist in the codebase
    • All props are defined accurately and each prop has a /** comment above it */
    • The file is named correctly
    • The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
    • The only data being stored in the state is data necessary for rendering and nothing else
    • For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
    • Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
    • All JSX used for rendering exists in the render method
    • The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions
  • If any new file was added I verified that:
    • The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory
  • If a new CSS style is added I verified that:
    • A similar style doesn't already exist
    • The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(themeColors.componentBG)
  • If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
  • If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
  • If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
  • If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
  • If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
  • If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
  • I have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.

Screenshots/Videos

Web
26998-web.mp4
Mobile Web - Chrome
26998-mobile-chrome.mp4
Mobile Web - Safari
26998-mobile-safari.MP4
Desktop
26998-desktop.mp4
iOS
26998-mobile-ios.MP4
Android
26998-mobile-android.mp4

@ntdiary
Copy link
Contributor

ntdiary commented Sep 19, 2023

  1. Make sure to log out.
  2. Refresh the page (for browser) or reopen the app (for native/desktop app).
  3. Log in with any account.
  4. Make sure device offline.
  5. Click plus button and then select Distance Request.
  6. Switch the device back online.
  7. Verify the map displays properly.

@pradeepmdk, let's update the Tests and QA steps. Since the previous address is cleared when re-logging in, we just need to verify the map renders properly. : )

Copy link
Contributor

@ntdiary ntdiary left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@hayata-suenaga, all yours! : )

@melvin-bot melvin-bot bot requested a review from hayata-suenaga September 19, 2023 10:39
@pradeepmdk
Copy link
Contributor Author

@ntdiary updated

@ntdiary
Copy link
Contributor

ntdiary commented Sep 22, 2023

@hayata-suenaga, kindly bump. : )

@pradeepmdk
Copy link
Contributor Author

@hayata-suenaga, bump;

@hayata-suenaga hayata-suenaga merged commit cd96293 into Expensify:main Sep 26, 2023
12 checks passed
@OSBotify
Copy link
Contributor

✋ This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

@OSBotify
Copy link
Contributor

🚀 Deployed to staging by https://github.com/hayata-suenaga in version: 1.3.75-0 🚀

platform result
🤖 android 🤖 success ✅
🖥 desktop 🖥 success ✅
🍎 iOS 🍎 success ✅
🕸 web 🕸 success ✅

@OSBotify
Copy link
Contributor

OSBotify commented Oct 2, 2023

🚀 Deployed to production by https://github.com/mountiny in version: 1.3.75-12 🚀

platform result
🤖 android 🤖 success ✅
🖥 desktop 🖥 success ✅
🍎 iOS 🍎 failure ❌
🕸 web 🕸 success ✅

@OSBotify
Copy link
Contributor

OSBotify commented Oct 2, 2023

🚀 Deployed to staging by https://github.com/hayata-suenaga in version: 1.3.76-0 🚀

platform result
🤖 android 🤖 success ✅
🖥 desktop 🖥 success ✅
🍎 iOS 🍎 success ✅
🕸 web 🕸 success ✅

@OSBotify
Copy link
Contributor

OSBotify commented Oct 3, 2023

🚀 Deployed to production by https://github.com/mountiny in version: 1.3.76-6 🚀

platform result
🤖 android 🤖 success ✅
🖥 desktop 🖥 success ✅
🍎 iOS 🍎 failure ❌
🕸 web 🕸 success ✅

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants