@CFDevelop As a reviewer would you not rather be taken in the journey with smaller PRs than a huge PR? In either scenario context is important... For me reviewing incremental changes (with the general idea of where something is going) is far less cognitively demanding than a large PR
Europe’s coolest alternative app marketplace is HERE!
Introducing AltStore PAL — an Apple-approved version of AltStore exclusive to the EU
Download now from our website for just €1.50/year (+ VAT) 🇪🇺 https://t.co/3ZfYbq4QNU
The recording of @tomdev_'s "Shifting Left with #Flutter" presentation from our most recent event is now available for everyone to learn from!
🚀https://t.co/CAr0JzYqFB📷
p.s. "Don't forget to smash that like button & subscribe!"
#FlutterDev#FlutterLearnFromExperts
@Frankdroid77 Thank you @Frankdroid77 🙂 just want to clarify that it's bringing quality concerns to left/earlier rather than bringing developer practices earlier, there just happens to be loads that developers can do to support this🙂
Thank you for coming!
@ICuvula If your onPopInvoked callback programatically pops then onPopInvoked is called a second time with didPop set as true.
Check out these 4 scenarios:
- canPop true
- canPop false
- canPop false then popping incorrectly
- canPop false then popping correctly
https://t.co/O469aUp2I9
E.g.
Version 1 - Available
Version 2 - Rolling out
Submit version 3 for review (even with managed publishing on)
Version 1 - Available
Version 2 - Halted, can't resume
Version 3 - Not yet published, but can halt, but halting doesn't resume version 2
PSA: Sending an app for review on Google Play before your previous version's rollout has completed (e.g. ramping up from 1% to 100% at your own pace) will halt the previous version with no way to resume
#androiddev#GooglePlay#flutter