Search results for query: *

Was it from 4.47am yesterday morning (is the time accurate on the device)?

Is it just hanging there?

we tried to take this over, but too many folks complained about not getting enough alerts ... withdrawals maybe, so that's on hold till after the flood.

it's supposed to ... but only if it seats right and what not .... did you see it now doing that? (if so dm device info)

to be honest, we know when you know ... the calling the csc tells us which you think is most important. rest assured, when one happens we know! (and want to make them not be)

good find, fix coming in that one

you should be able to hit pause in a flow and go do a thing wo having to leave altogether. we are not waiting as long as myWork did for a printing response and that's causing print fun.

that'll be addressed soon. specifically the not being clear what happens when failure happens, and what you are supposed to do when it happens. ideally it'd never happen, but that's not a good way to plan. loading tasks to be done used to be a load issue, shouldn't be anymore (except for...

glad we got it in ... 28 is on its heels (fixing some of the pricing issues and more)

I appreciate the grace there, and the headroom to work out kinks ... but we still shouldn't crash (at least not for long) :) better builds coming in hot

it should just update sfq (or not) based on your answer ...

looking...

grab then and DM when u have the situation. if you are able, I can check your device live (if you're comfortable making that connection), if not we'll keep digging. grab the detailed err screens

froze, then you went back into batch.... how'd you get back? back button, or killed the app, or..?

the freezing you see ... it looks like it's trying to load but never does right? if so, that's the one we're chasing. I think it's going to take us with a dev build working in a store to lock it down. which we do if this week isn't fruitful. there's something about the organic movement...

today was ... not great. tomorrow will be better (?)

done. it'll be in the next build.

thanks for the feedback folks, we're shipping another go starting tomorrow to deal w some of the non-response on move things ... this one I hadn't heard... next time that happens call it in please, the process stuff I have to let work out with all the people that get a say, but crashes...

should have been or, the thing that was preventing them from showing at all was addressed. have you seen none after trying a few?

give it a go and let me know what you experience vs what you expected. if love to hear a fresh take (frustrated or satisfied).