38 KiB
[0:00 - 0:11] We feel that the list of issues we're going to review in a couple minutes, we do not have enough time to test it properly and be confident enough that it's going to be solid for submission.
[0:22 - 0:26] Because those issues need to be resolved before we submit.
[0:28 - 0:31] Once we submit that, we'll do a freeze and we'll talk about it.
[0:11 - 0:22] So we'll go through all of that with you, if you can give us an update, not necessarily the detail of it, but letting us know when do you think those are going to be resolved.
[0:31 - 0:39] Once we review the states of those issues, we'd like to discuss about potential submission date.
[0:39 - 0:52] And the issue, we want to dive more about the migration issue of people when they're logging on one device and they have another account on a different device, we'll go through that.
[0:52 - 0:56] Yes, but let's go first on the disturb issues.
[0:57 - 1:00] And I want to leave it to Carrie.
[1:00 - 1:01] Okay.
[1:01 - 1:09] So according to my list, and as you mentioned, Julie, we have the migration test that we did.
[1:09 - 1:11] I think you received my email last night.
[1:11 - 1:12] Yes.
[1:12 - 1:14] Yes, I did.
[1:18 - 1:21] We are looking into what's going on there.
[1:21 - 1:32] We tested on test and gave you the UAT one pretty quickly.
[1:32 - 1:36] Again, because we were trying to get through the deadline.
[1:36 - 1:43] So we're going to be looking over what was going on on UAT because it was working clearly on test.
[1:43 - 1:49] I do not perceive this to be a major problem by any stretch.
[1:49 - 1:58] It looks like it's like some sort of, I don't have the exact details we have.
[1:58 - 2:04] My developer hasn't come back with the specifics of the problem yet.
[2:04 - 2:07] But we are looking into it.
[2:07 - 2:11] It did test cleanly for us on staging.
[2:12 - 2:18] And again, I think we sent that to you just as quickly as we did because you're so close to the deadline.
[2:18 - 2:26] We would have loved to have had more time to test before we sent it to you.
[2:26 - 2:37] But with not a submission on Monday, we can take, go in, do another pass, and make sure it's completely stable before we get it.
[2:42 - 2:50] So in short version, I do not know what the technical problem is yet.
[2:50 - 2:53] My team hasn't come back to me yet.
[2:53 - 3:04] But based on our results on tests, we're confident that we can, if we have a little bit of time, we can get you a very stable version to work
[3:08 - 3:15] Okay, so the second point is the user last activity at field.
[3:15 - 3:24] So it doesn't seem to be reliable now, according to our emails.
[3:24 - 3:33] And we'd like to have your thoughts about a more robust approach or visibility to that field.
[3:43 - 3:58] Anytime the user touches the screen, it checks to see if at least an hour has passed since the user has done anything.
[3:33 - 3:43] Okay, so right at the moment, the way it works is we have a system that detects user interactions on the screen.
[3:58 - 4:08] And if an hour has passed since the last time they interacted, our backend receives a message saying it's a new session.
[4:08 - 4:18] What we can do is basically we can check to see whether or not that network call succeeded.
[4:18 - 4:32] And if the network call didn't succeed, just send a message on the next interaction and just keep trying interaction after interaction to make sure that...
[4:32 - 4:38] ...and basically we'd be using a retrop.
[4:38 - 4:41] It would be what it would work with.
[4:41 - 4:44] I think this is...
[4:44 - 4:50] I'm trying to think of what else we could do.
[4:50 - 5:02] We could try to cache the idea of a session and on the next network call out, send an update.
[5:02 - 5:15] But I think simply the other approach just with a retry, the only way that's going to fail is with a network error problem.
[5:15 - 5:17] Otherwise, it's going to go through.
[5:17 - 5:25] So I think that is probably the most...
[5:25 - 5:31] Kind of a combination of clean, simple and stable.
[5:31 - 5:39] I do question the fact that do we need the hour specifically or do we need the date?
[5:39 - 5:43] I think we need more the date than the actual hour.
[5:43 - 5:47] No, we marked the time stamp.
[5:47 - 5:49] Oh, okay.
[5:49 - 5:51] The hour simply is...
[5:51 - 5:57] Okay, I guess I'll take one step back and explain there.
[5:57 - 6:06] What we're trying to do with this is track the start of sessions that a user has started a session.
[6:06 - 6:07] Gotcha.
[6:07 - 6:08] Okay.
[6:08 - 6:29] So, would a retry be sufficient?
[6:29 - 6:42] A second option would be for your test team for visibility.
[6:42 - 6:55] We could, on non-dev builds, put an indicator so that you could see in the app when we sent the message last.
[6:55 - 6:57] So you could compare that with your results.
[6:57 - 7:02] And that would be a testing-only tool.
[7:02 - 7:11] Yeah, I'm just trying to think of what would give you the most confidence that this system is working.
[7:11 - 7:18] Since it's an analytic system that really just sends a message out periodically that is invisible to the user.
[7:18 - 7:25] The retry should be very...
[7:25 - 7:28] make the system very reliable.
[7:28 - 7:29] I just...
[7:38 - 7:56] i'll let habiba decide about that but she may want more visibility uh eventually yeah okay um what i'm just thinking through a uh yeah we uh we we can definitely do something okay
[7:29 - 7:32] do you want some sort of additional visibility above it?
[8:00 - 8:08] Is it possible to have maybe a meeting with Abiba and your team to work through a robust solution?
[8:08 - 8:15] Because I personally need to know if it's going to be a solid solution that fits what we want.
[8:15 - 8:16] Yep, absolutely.
[8:16 - 8:26] We can meet with her and discuss what would make her feel confident with the system.
[8:30 - 8:39] So the other point is about the forced migration and the multi-device user.
[8:39 - 8:47] For sure, we need from our end a solid communication plan, especially with the school.
[8:47 - 8:56] We are also exploring another solution, but for us, it's a critical point.
[8:56 - 8:57] Yeah, that makes sense.
[8:58 - 9:06] We're going to discuss today the ideal solution we have in mind and see if it's feasible.
[9:06 - 9:11] Hopefully today, we're trying to have this conversation today, if not hopefully Monday.
[9:11 - 9:22] And we'll let you know, because it depends if we go option A, it's easy, we can move forward without no issue.
[9:22 - 9:27] Option B, we'll have to time it properly with when communication are sending out and blah, blah, blah.
[9:31 - 9:35] But that's going to be something critical to define when we submit.
[9:28 - 9:31] So we'll get back to you on which solution we go with.
[9:35 - 9:37] Okay, that makes sense.
[9:41 - 9:48] And the last point, if I'm not wrong, it's about Salesforce tests.
[9:48 - 9:53] This morning, the test didn't go through either.
[9:53 - 9:58] And I know that Nicolas and our expert is in touch about this point.
[9:58 - 10:04] Yeah, I saw that the messages were going back and forth.
[10:04 - 10:10] I didn't look closely because they seem to have them under control.
[10:10 - 10:16] I'll check in with Nicolas to see where he's at with his communications with Mark.
[10:16 - 10:34] And it looked like there was a question of data going from one part of Salesforce to another part of Salesforce.
[10:36 - 10:40] That was what I was seeing was the issue.
[10:50 - 10:52] Okay.
[10:52 - 10:57] And I don't know, Julie, if you want to mention something about the frequency of the data.
[10:57 - 10:59] I'll dig in a little bit more.
[10:59 - 11:01] I'll dig in a little bit more.
[11:01 - 11:03] I'll dig in a little bit more.
[11:03 - 11:04] I'll dig in a little bit more.
[11:04 - 11:05] I'll dig in a little bit more.
[11:06 - 11:07] I'll dig in a little bit more.
[11:07 - 11:08] I'll dig in a little bit more.
[11:08 - 11:09] I'll dig in a little bit more.
[11:05 - 11:06] I'll dig in a little bit more.
[11:09 - 11:10] I'll dig in a little bit more.
[11:10 - 11:11] I'll dig in a little bit more.
[11:11 - 11:12] I'll dig in a little bit more.
[11:12 - 11:13] I'll dig in a little bit more.
[11:13 - 11:15] I'll dig in a little bit more.
[11:15 - 11:17] I'll dig in a little bit more.
[11:17 - 11:19] I'll dig in a little bit more.
[11:19 - 11:20] I'll dig in a little bit more.
[11:20 - 11:21] I'll dig in a little bit more.
[11:21 - 11:22] I'll dig in a little bit more.
[11:22 - 11:23] I'll dig in a little bit more.
[11:23 - 11:24] I'll dig in a little bit more.
[11:24 - 11:25] I'll dig in a little bit more.
[11:25 - 11:26] I'll dig in a little bit more.
[11:26 - 11:27] I'll dig in a little bit more.
[11:27 - 11:29] I'll dig in a little bit more.
[11:29 - 11:31] I'll dig in a little bit more.
[11:31 - 11:33] I'll dig in a little bit more.
[11:33 - 11:34] I'll dig in a little bit more.
[10:42 - 10:50] I'll dig in a little bit deeper and check in with Nicolas and get you some sort of update.
[11:35 - 11:36] I'll dig in a little bit more.
[11:34 - 11:35] I'll dig in a little bit more.
[11:36 - 11:37] I'll dig in a little bit more.
[11:37 - 11:38] I'll dig in a little bit more.
[11:40 - 11:41] I'll dig in a little bit more.
[11:39 - 11:40] I'll dig in a little bit more.
[11:42 - 11:43] I'll dig in a little bit more.
[11:41 - 11:42] I'll dig in a little bit more.
[11:43 - 11:44] I'll dig in a little bit more.
[11:38 - 11:39] I'll dig in a little bit more.
[11:44 - 11:45] I'll dig in a little bit more.
[11:45 - 11:46] I'll dig in a little bit more.
[11:47 - 11:48] I'll dig in a little bit more.
[11:48 - 11:49] I'll dig in a little bit more.
[11:49 - 11:50] I'll dig in a little bit more.
[11:57 - 11:58] I'll dig in a little bit more.
[11:46 - 11:47] I'll dig in a little bit more.
[11:58 - 11:59] I'll dig in a little bit more.
[11:59 - 12:00] I'll dig in a little bit more.
[12:01 - 12:02] I'll dig in a little bit more.
[12:02 - 12:03] I'll dig in a little bit more.
[12:00 - 12:01] I'll dig in a little bit more.
[12:07 - 12:08] I'll dig in a little bit more.
[12:08 - 12:09] I'll dig in a little bit more.
[12:09 - 12:10] I'll dig in a little bit more.
[12:10 - 12:11] I'll dig in a little bit more.
[12:11 - 12:12] I'll dig in a little bit more.
[12:12 - 12:13] I'll dig in a little bit more.
[12:03 - 12:04] I'll dig in a little bit more.
[12:13 - 12:14] I'll dig in a little bit more.
[12:14 - 12:15] I'll dig in a little bit more.
[12:15 - 12:16] I'll dig in a little bit more.
[12:16 - 12:17] I'll dig in a little bit more.
[12:27 - 12:28] I'll dig in a little bit more.
[12:28 - 12:29] I'll dig in a little bit more.
[12:29 - 12:30] I'll dig in a little bit more.
[12:31 - 12:32] I'll dig in a little bit more.
[12:32 - 12:33] I'll dig in a little bit more.
[12:33 - 12:34] I'll dig in a little bit more.
[12:34 - 12:35] I'll dig in a little bit more.
[12:35 - 12:36] I'll dig in a little bit more.
[12:36 - 12:37] I'll dig in a little bit more.
[12:06 - 12:07] I'll dig in a little bit more.
[12:37 - 12:38] I'll dig in a little bit more.
[12:30 - 12:31] I'll dig in a little bit more.
[12:39 - 12:40] I'll dig in a little bit more.
[12:38 - 12:39] I'll dig in a little bit more.
[12:41 - 12:42] I'll dig in a little bit more.
[12:42 - 12:43] I'll dig in a little bit more.
[12:40 - 12:41] I'll dig in a little bit more.
[12:43 - 12:44] I'll dig in a little bit more.
[12:44 - 12:45] I'll dig in a little bit more.
[12:57 - 12:58] I'll dig in a little bit more.
[12:46 - 12:47] I'll dig in a little bit more.
[12:58 - 12:59] I'll dig in a little bit more.
[12:59 - 13:00] I'll dig in a little bit more.
[13:00 - 13:01] I'll dig in a little bit more.
[13:01 - 13:02] I'll dig in a little bit more.
[13:03 - 13:04] I'll dig in a little bit more.
[13:02 - 13:03] I'll dig in a little bit more.
[13:04 - 13:05] I'll dig in a little bit more.
[13:05 - 13:06] I'll dig in a little bit more.
[13:06 - 13:07] I'll dig in a little bit more.
[13:07 - 13:08] I'll dig in a little bit more.
[13:08 - 13:09] I'll dig in a little bit more.
[13:09 - 13:10] I'll dig in a little bit more.
[13:10 - 13:11] I'll dig in a little bit more.
[13:11 - 13:12] I'll dig in a little bit more.
[13:12 - 13:13] I'll dig in a little bit more.
[13:13 - 13:14] I'll dig in a little bit more.
[13:14 - 13:15] I'll dig in a little bit more.
[13:15 - 13:16] I'll dig in a little bit more.
[13:16 - 13:17] I'll dig in a little bit more.
[13:27 - 13:28] I'll dig in a little bit more.
[13:28 - 13:29] I'll dig in a little bit more.
[13:29 - 13:30] I'll dig in a little bit more.
[13:30 - 13:31] I'll dig in a little bit more.
[13:31 - 13:32] I'll dig in a little bit more.
[13:33 - 13:34] I'll dig in a little bit more.
[13:32 - 13:33] I'll dig in a little bit more.
[13:35 - 13:36] I'll dig in a little bit more.
[13:34 - 13:35] I'll dig in a little bit more.
[13:36 - 13:37] I'll dig in a little bit more.
[13:37 - 13:38] I'll dig in a little bit more.
[13:38 - 13:39] I'll dig in a little bit more.
[12:45 - 12:46] I'll dig in a little bit more.
[13:39 - 13:40] I'll dig in a little bit more.
[13:40 - 13:41] I'll dig in a little bit more.
[13:43 - 13:44] I'll dig in a little bit more.
[13:42 - 13:43] I'll dig in a little bit more.
[13:44 - 13:45] I'll dig in a little bit more.
[13:45 - 13:46] I'll dig in a little bit more.
[13:46 - 13:47] I'll dig in a little bit more.
[13:57 - 13:58] I'll dig in a little bit more.
[13:58 - 13:59] I'll dig in a little bit more.
[13:59 - 14:00] I'll dig in a little bit more.
[14:00 - 14:01] I'll dig in a little bit more.
[14:01 - 14:02] I'll dig in a little bit more.
[14:02 - 14:03] I'll dig in a little bit more.
[14:03 - 14:04] I'll dig in a little bit more.
[14:04 - 14:05] I'll dig in a little bit more.
[14:06 - 14:07] I'll dig in a little bit more.
[14:05 - 14:06] I'll dig in a little bit more.
[14:07 - 14:08] I'll dig in a little bit more.
[14:08 - 14:09] I'll dig in a little bit more.
[14:09 - 14:10] I'll dig in a little bit more.
[14:10 - 14:11] I'll dig in a little bit more.
[14:11 - 14:12] I'll dig in a little bit more.
[14:12 - 14:13] I'll dig in a little bit more.
[14:13 - 14:14] I'll dig in a little bit more.
[14:14 - 14:15] I'll dig in a little bit more.
[13:41 - 13:42] I'll dig in a little bit more.
[14:15 - 14:16] I'll dig in a little bit more.
[14:16 - 14:17] I'll dig in a little bit more.
[14:28 - 14:29] I'll dig in a little bit more.
[14:29 - 14:30] I'll dig in a little bit more.
[14:30 - 14:31] I'll dig in a little bit more.
[14:31 - 14:32] I'll dig in a little bit more.
[14:32 - 14:33] I'll dig in a little bit more.
[14:33 - 14:34] I'll dig in a little bit more.
[14:34 - 14:35] I'll dig in a little bit more.
[14:35 - 14:36] I'll dig in a little bit more.
[14:36 - 14:37] I'll dig in a little bit more.
[14:37 - 14:38] I'll dig in a little bit more.
[14:38 - 14:39] I'll dig in a little bit more.
[14:39 - 14:40] I'll dig in a little bit more.
[14:40 - 14:41] I'll dig in a little bit more.
[14:41 - 14:42] I'll dig in a little bit more.
[14:42 - 14:43] I'll dig in a little bit more.
[14:43 - 14:44] I'll dig in a little bit more.
[14:44 - 14:45] I'll dig in a little bit more.
[14:45 - 14:46] I'll dig in a little bit more.
[14:46 - 14:47] I'll dig in a little bit more.
[12:05 - 12:06] I'll dig in a little bit more.
[14:57 - 14:59] Okay.
[15:01 - 15:09] Okay, we'll mark that down and distribute that internally.
[15:09 - 15:12] So a lot more time than we wanted initially.
[15:12 - 15:13] Yes, I understand.
[15:13 - 15:24] I think it is a good chance that we will be able to have it to you by Friday next week.
[15:25 - 15:38] Just, I want, if we do find any other problems, I wouldn't want to surprise you with them.
[14:27 - 14:28] I'll dig in a little bit more.
[15:38 - 15:43] So that's why I would say the possibility of falling into the week after.
[15:45 - 15:49] Okay, so I mark down the date.
[15:53 - 15:55] I will confirm to you through email.
[15:55 - 15:56] Yeah.
[15:49 - 15:53] I will confirm, like last time, we'll discuss internally.
[15:56 - 15:57] What we're comfortable with.
[15:57 - 16:05] And something will give a go on the freeze because we really want, at one point, we need to freeze.
[16:10 - 16:11] Yeah.
[16:13 - 16:14] Okay.
[15:43 - 15:45] Okay.
[16:14 - 16:14] Okay.
[16:14 - 16:14] Okay.
[16:05 - 16:10] We cannot just go on with the additional back coming in and stuff.
[16:17 - 16:29] When we discuss about the solution we have in mind when it comes to user upgrading the app, updating the app?
[16:30 - 16:30] Mm-hmm.
[16:30 - 16:34] Would it help you if we share with you our solution?
[16:14 - 16:17] Will it help you to know about what I discussed?
[16:34 - 16:35] Yes.
[16:35 - 16:36] Yes.
[16:30 - 16:30] Mm-hmm.
[16:36 - 16:37] Yes.
[12:04 - 12:05] I'll dig in a little bit more.
[16:37 - 16:38] What you have in mind?
[16:38 - 16:39] Yep.
[16:36 - 16:36] Yes.
[16:40 - 16:40] Okay.
[16:40 - 16:41] Okay.
[17:02 - 17:06] There is no other option for everybody to update their app.
[17:06 - 17:11] We don't have to send any communication because they're just going to have to re-log in.
[16:39 - 16:40] That would be very useful.
[17:11 - 17:13] So that's what we are exploring to see.
[17:01 - 17:02] Yeah.
[16:53 - 17:01] Once everybody is disconnected, the moment they will have to log in to have a message saying, hey, you have to update like this.
[17:13 - 17:19] Do they have a way to disconnect all users and change the message when they try to log in?
[17:19 - 17:21] Yeah.
[17:25 - 17:32] Like we've been looking for things that didn't involve changing the old app.
[17:32 - 17:45] But if changing the old app to have a message, especially one that can be turned on from Contentful, that is a very strong solution.
[17:22 - 17:25] That's actually probably the simplest solution.
[17:45 - 17:51] And probably the best case.
[17:51 - 17:52] Yeah.
[17:52 - 17:52] Yeah.
[17:52 - 17:57] And if it's not, so we are trying to get in touch with them and have that discussed.
[17:57 - 18:06] If not, plan B will be to arrange communication through emails, communication through a notification message in the app.
[18:07 - 18:15] And then the timing when we send the app and when the app update and all of that.
[18:15 - 18:21] So hopefully we don't have to go through that to be more chaotic, but we'll let you know.
[18:22 - 18:22] Yeah.
[18:22 - 18:22] Yeah.
[18:22 - 18:22] Yeah.
[18:22 - 18:25] That would simplify things considerably.
[18:26 - 18:27] Okay.
[18:27 - 18:27] Okay.
[18:27 - 18:30] So we'll continue about that.
[18:30 - 18:33] Yeah.
[18:33 - 18:34] So we'll get back to you on the date.
[18:34 - 18:44] Tell us, like, and reach out to Carol and Abdullai when you're ready to do a delivery.
[18:44 - 18:47] The back-end delivery is not an issue for us because it's automatic.
[18:47 - 18:51] So I know you've been sending multiple back-end delivery.
[18:51 - 18:52] And it's fine.
[18:52 - 18:54] It's manageable because it's automatic.
[18:54 - 18:59] For the rest, please ask the goal to the team and the whole engineer if they're ready.
[19:00 - 19:15] And so I think once they do the test and then bring back to your team some bugs or fix that needs to be done, same thing to ask the goal before the second delivery after that kind of fix to make sure we are ready to receive it and to test for them.
[18:25 - 18:26] Yeah.
[19:15 - 19:16] Okay.
[19:16 - 19:17] That makes perfect sense.
[16:41 - 16:53] So right now, it's Amadou at the idea where we are going to reach out to our current agency that is the Noling Bookie at this time and ask to force the disconnection for all users.
[19:17 - 19:20] I will mention it in my email before then.
[19:20 - 19:21] Yeah.
[19:33 - 19:39] We'll communicate with you that we are at the end of our process.
[19:30 - 19:33] And then we'll do a regression test.
[19:21 - 19:30] So we'll keep working until we have all the items that we're currently aware of resolved.
[19:39 - 19:41] You'll tell us that you're ready to receive.
[19:41 - 19:43] You'll check it.
[19:44 - 19:51] We'll probably then start work on a second branch on phase two while we wait for your results.
[20:01 - 20:02] If there are, we fix it.
[20:02 - 20:03] Okay.
[20:03 - 20:07] Do I miss anything?
[20:07 - 20:09] Caroline and Andrew?
[20:09 - 20:12] No.
[20:12 - 20:12] No.
[20:12 - 20:13] Okay.
[20:14 - 20:14] Okay.
[20:14 - 20:21] So I will send you an email within the afternoon to confirm the dates we're comfortable with.
[20:21 - 20:23] And that's it?
[20:23 - 20:24] Yep.
[19:51 - 19:56] None of that phase two work will go into phase one.
[20:24 - 20:34] And we'll keep working and get all of the remaining issues fixed and a clean and stable build in your hands.
[20:34 - 20:35] So that we can listen.
[20:35 - 20:36] Perfect.
[20:38 - 20:38] Bye.
[20:38 - 20:38] Bye.
[20:36 - 20:36] Thank you so much.
[20:38 - 20:39] Bye.
[20:39 - 20:39] Bye.
[20:39 - 20:39] Bye.
[20:44 - 20:45] Thank you.
[19:56 - 20:01] If there's no problems from your side, then we move forward.
[0:00 - 0:11] We feel that the list of issues we're going to review in a couple minutes, we do not have enough time to test it properly and be confident enough that it's going to be solid for submission.
[0:11 - 0:15] So we'll go through all of that with you.
[0:15 - 0:26] If you can give us an update, not necessarily the detail of it, but letting us know when do you think those are going to be resolved, because those issues need to be resolved before we submit.
[0:31 - 0:51] Once we review the states of those issues, we'd like to discuss about potential submission date and the issue we want to dive more about the migration issue of people when they're logging on one device and they have another account on a different device.
[0:51 - 0:52] We'll go through that.
[0:52 - 0:56] Yes, but let's go first on the list of issues.
[0:57 - 0:59] And I will leave it to Carol.
[0:59 - 1:00] Okay.
[1:00 - 1:08] So according to my list, and as you mentioned, Julie, we have the migration test that we did.
[1:11 - 1:14] Yes, I did.
[1:08 - 1:11] I think you received my email last night.
[1:17 - 1:21] We are looking into what's going on there.
[1:21 - 1:31] We tested on test and gave you the UAT one pretty quickly.
[1:31 - 1:35] Again, because we were trying to get through the deadline.
[1:35 - 1:42] So we're going to be looking over what was going on on UAT because it was working clearly on test.
[1:42 - 1:48] I do not foresee this to be a major problem by any stretch.
[1:48 - 1:57] It looks like it's like some sort of, I don't have the exact details we have.
[1:57 - 2:06] My developer hasn't come back with the specifics of the problem yet, but we are looking into it.
[2:06 - 2:10] It did test cleanly for us on staging.
[20:36 - 20:38] Thank you.
[0:27 - 0:31] Once we submit that, we'll do a freeze and we'll talk about it.
[2:17 - 2:25] We would have loved to have had more time to test before we sent it to you.
[2:10 - 2:17] And again, I think we sent that to you just as quickly as we did because we're so close to the deadline.
[2:50 - 3:03] But based on our results on tests, we're confident that we can, if we have a little bit of time, we can get you a very stable version to work.
[2:48 - 2:50] My team hasn't come back to me yet.
[3:13 - 3:23] So it doesn't seem to be reliable now, according to our emails.
[3:07 - 3:13] Okay, so the second point is the user last activity at field.
[3:23 - 3:31] And we'd like to have your thoughts about a more robust approach or visibility to that field.
[3:32 - 3:42] Okay, so right at the moment, the way it works is we have a system that detects user interactions on the screen.
[3:42 - 3:55] Anytime the user touches the screen, it checks to see if at least an hour has passed since the user has done anything.
[3:55 - 4:06] And if an hour has passed since the last time they interacted, our backend receives a message saying it's a new session.
[4:07 - 4:16] So what we can do is basically we can check to see that the net, whether or not that network call succeeded.
[4:16 - 4:29] And if the network call didn't succeed, just send a message on the next interaction and just keep trying interaction after interaction to make sure that.
[4:31 - 4:39] And basically we'd be using a retry would be what it would work with.
[2:42 - 2:48] So in short version, I do not know what the technical problem is yet.
[4:39 - 4:43] I think this is...
[4:43 - 4:49] I'm trying to think of what else we could do.
[4:51 - 5:01] We could try to cache the idea of a session and on the next network call out, send an update.
[5:01 - 5:14] But I think simply the other approach, just with a retry, the only way that's going to fail is with a network error problem.
[2:25 - 2:36] But with not a submission on Monday, we can take, go in, do another pass, and make sure it's completely stable before we send it to you.
[5:14 - 5:16] Otherwise it's going to go through.
[5:42 - 5:45] So we mark the timestamp.
[5:45 - 5:56] So the hour simply is on-- OK, I guess I'll take one step back and explain there.
[5:56 - 6:05] What we're trying to do with this is track the start of sessions that a user has started a session.
[6:15 - 6:18] Yeah, and on web, that's why we're using the one app.
[6:18 - 6:19] It is for web.
[6:05 - 6:15] On mobile, that's really easy because the app will get shut down by the operating system.
[6:19 - 6:28] So would a retry be sufficient?
[6:41 - 6:54] We could, on non-dev builds, put an indicator so that you can see in the app when we sent the message last.
[6:28 - 6:41] A second option would be for your test team for visibility.
[6:54 - 6:57] So you can compare that with your results.
[6:57 - 7:00] And that would be a testing-only tool.
[7:00 - 7:16] Yeah, I'm just trying to think of what would give you the most confidence that this system is working since it's an analytic system that really just sends a message out periodically that is invisible to the user.
[7:16 - 7:26] The retry should make the system very reliable.
[7:26 - 7:29] I just-- do you want some sort of additional visibility above and beyond?
[7:42 - 7:43] Okay.
[7:43 - 7:49] I'm just thinking through a...
[7:49 - 7:53] Yeah, we can definitely do something like that.
[8:04 - 8:11] Because I personally need to know if it's going to be a solid solution that fits what we want.
[7:53 - 8:04] Is it possible to have maybe a meeting with Abiba and your team to work through a robust solution?
[8:11 - 8:13] Yep, absolutely.
[8:13 - 8:22] We can meet with her and discuss what would make her feel confident with the system.
[8:27 - 8:36] So the other point, it's about the forced migration and the multi-device user.
[8:36 - 8:44] For sure, we need from our end a solid communication plan, especially with the school.
[8:44 - 8:52] We are also exploring another solution, but for us, it's a critical point.
[8:52 - 8:54] Yeah, that makes sense.
[8:55 - 9:03] We're going to discuss today the ideal solution we have in mind and see if it's feasible.
[9:03 - 9:08] Hopefully today, we're trying to have this conversation today, if not hopefully Monday.
[9:08 - 9:17] And we'll let you know because it depends if we go option A, it's easy.
[5:16 - 5:29] So I think that is probably the most kind of a combination of clean, simple and stable.
[9:17 - 9:18] We can move forward without no issue.
[9:18 - 9:24] Option B, we'll have to time it properly with when communication are sending out and blah, blah, blah.
[9:27 - 9:31] But that's going to be something critical to define when we submit.
[9:32 - 9:33] Okay, that makes sense.
[9:33 - 9:44] And the last point, if I'm not wrong, it's about Salesforce tests.
[9:44 - 9:47] I know that we're going to be able to do that.
[9:47 - 9:49] I know that we're going to be able to do that.
[9:24 - 9:27] So we'll get back to you on which solution we go with.
[9:49 - 9:51] And I know that we're going to be able to do that.
[9:51 - 9:53] And I know that we're going to be able to do that.
[8:22 - 8:23] Okay.
[9:55 - 9:57] And I know that we're going to be able to do that.
[9:57 - 10:01] I saw that the messages were going back and forth.
[10:13 - 10:30] And it looked like there was a question of data going from one part of Salesforce to another part of Salesforce.
[10:06 - 10:12] I'll check in with Nicholas to see where he's at with his communications with Mark.
[10:30 - 10:36] What I was seeing was the issue.
[10:36 - 10:37] So we can have a...
[10:37 - 10:46] I'll dig in a little bit deeper and check in with Nicholas and get you some sort of update.
[10:46 - 10:48] Okay.
[10:48 - 10:53] And I don't know, Julie, if you want to mention something about the frequency of the delivery.
[10:01 - 10:06] I didn't look closely because they seem to have that under control.
[10:53 - 11:01] So just to be clear, so there's the issue with the migration communication that's on our hand for now.
[11:06 - 11:13] We agree internally that once those are fixed, we want to freeze the code.
[11:13 - 11:14] We don't want to go further.
[11:14 - 11:17] And if we go further, it will be on a different branch.
[11:17 - 11:21] We want to make sure that beyond that, there's no other issue that is controlled.
[11:21 - 11:29] We realized last communication we had, remember, we say, have a delivery bill on Wednesday.
[11:29 - 11:35] I understand that because we had in mind to submit on Monday that there was mobile delivery.
[11:35 - 11:42] But internally, it's creating some type of noise and complication to having like ongoing delivery.
[11:42 - 11:45] We need to restart the test and it's not efficient.
[11:45 - 11:53] So we would like to be more in control of the delivery where we agree to have all those issues fixed in the delivery that we will let you know.
[11:53 - 11:53] We will let you know.
[11:01 - 11:06] The rest of the list is the remaining issue we want to fix before submission.
[11:53 - 11:55] We will let you know.
[12:00 - 12:04] And once you're ready to deliver, we can ask Carol and Abdullai.
[11:55 - 12:00] We will let you tell us when you think all of that can be fixed and delivered.
[5:29 - 5:32] Um,
[12:04 - 12:10] We can give you the goal to do the delivery and do the delivery based on goal, no goal.
[12:10 - 12:14] Like this, we can control internally if we have the resources to test and all of that.
[12:18 - 12:20] That would be straightforward.
[12:17 - 12:18] Absolutely.
[12:20 - 12:20] Okay.
[9:53 - 9:55] And I know that we're going to be able to do that.
[12:20 - 12:24] Like this, we don't do multiple delivery that are confusing.
[12:24 - 12:34] So do you have an idea of when you will be able to have a delivery with those main issues covered and fixed?
[12:45 - 12:53] We have, we don't have a lot of items left in dev.
[12:35 - 12:45] So I haven't looked at your board, but based off of our board, which should mirror the same issues.
[12:56 - 12:56] Okay.
[12:56 - 13:11] So I think the short answer is end of next week up to the middle of the week after this would be all issues that we currently have done.
[12:34 - 12:35] Okay.
[13:16 - 13:30] Our testing team getting through all of the items in testing, because right at the moment, dev is well ahead of testing and we have a backlog of testing tickets.
[13:11 - 13:16] And that should be by like, maybe Tuesday or Wednesday.
[13:44 - 13:54] So that to me would be probably Friday at the earliest, maybe Tuesday after that at the latest.
[13:36 - 13:44] And then we'd want to do a, an end to end pass before we hand it to you.
[13:55 - 13:59] So I mean Friday the 18th to Tuesday the 22nd.
[13:30 - 13:36] They'd probably be done Thursday or Friday.
[13:59 - 14:00] Yeah.
[12:14 - 12:17] So would it work for you?
[14:00 - 14:08] Maybe I'll be, I'll be cautious and say that Wednesday the 23rd, just to be on, be on the cautious side.
[14:16 - 14:43] I think we would be confident in giving you builds that are not just every ticket tested, but us having gone through every ticket completed, every ticket tested and a full regression pass with a little bit of margin of error for us having found a couple extra things.
[14:49 - 14:54] Okay.
[14:54 - 14:56] Um, um,
[14:59 - 20:01] we'll mark that down and uh just put that internally so a lot more time that we wanted initially yes i understand um i think is a good chance that we would be able to have it to you by friday uh friday next week uh just i would i love i want um if we do find any other problems i wouldn't want to surprise you with them so that's why i would uh say the possibility of falling into the week after okay uh okay so i mark down the date um i will confirm like last time we'll discuss internally i will confirm to you through email yeah what we're comfortable with um and something will give a go on the freeze because we really want at one point we need to freeze we cannot just go on with the additional bug coming in stuff um okay will they help you to know about what i discussed uh when we discussed about the the solution the solution we have in mind when it comes to user upgrading the uh updating that's a great updating the app would it help you if we share with you our solution i guess uh if what you have in mind that would be very useful okay so right now it's amadu at the idea where we are going to reach out to our current uh agency that is handling bookie at this time and ask to force the disconnection for all users once everybody is disconnected the moment they will have to log in to have a messaging hey you have to update like this there is no other option for everybody to update their app we don't have to send any communication because they're just going to have to re-log in so that's what we are exploring to see do they have a way to disconnect all users and change the message when they try to log in yeah that uh that's actually probably the simplest solution like we been looking for things that didn't involve changing the old uh the old app um but if changing the old app to have a message especially one that could be turned on from contentful uh that is a that is a very strong solution um and uh probably the best case yeah and if it's not so we're trying to get in touch with them and have that discussed if not plan b will be to arrange communication through emails communication through a notification message in the app and then the timing on when we send the communication through when we submit the app and when they have to update and all of that so hopefully we don't have to go through that it's a bit more chaotic but oh we'll let you know yeah that that would simplify things uh considerably so yeah okay okay so we'll uh um yeah so we'll get back to you on the date uh tell us like and reach out to carol and abdulai when you're ready to do a delivery the back-end delivery is not an issue for us because it's automatic so i know you've been sending multiple delivery back-end delivery and it's fine it's manageable because it's automatic for the rest please ask the goal to the team and they will let you know if they're ready uh and something once they do the test and then bring back to your team some bugs or fix that needs to be done uh same thing to ask the goal before the second delivery after that's the final thing to make sure we're ready to receive it and to test properly okay that makes perfect sense i will mention it in my email regardless okay so uh we'll keep working until we have all the items that uh we're currently aware of uh results uh and then we'll do a regression test we'll communicate with you that we are at the end of our process you'll tell us that you're ready to receive you'll check it uh we'll probably then start work on a second branch on phase two uh while we wait for your results uh none of that phase two work would go into phase one if there's no problems from your side then we move forward if there are we fix them okay do i do i miss anything carol and amandri
[20:01 - 20:35] no good for me okay so i will send you an email in within the afternoon to confirm the dates we're comfortable with and and that's it yep and we'll uh we'll keep working and get all of the remaining issues fixed uh and a clean and stable build in your hands so that we can release this perfect thank you so much thank you
[14:43 - 14:49] That's the timeframe that I would be confident in this being done.
[14:08 - 14:13] I think we would.