• Breaking News

    Wednesday, April 6, 2022

    Home Unlabelled Android Dev - I paid a fee to register my dev account. Google refused to verify it or return my money back.

    Android Dev - I paid a fee to register my dev account. Google refused to verify it or return my money back.

    April 06, 2022

    Android Dev - I paid a fee to register my dev account. Google refused to verify it or return my money back.

    I paid a fee to register my dev account. Google refused to verify it or return my money back.

    Posted: 06 Apr 2022 12:27 AM PDT

    I'm not sure what to do, hopefully, somebody can help me here.

    I have an app that I worked on for months. When it got ready I've registered a company and created Apple and Google Play developer accounts.

    Both platforms required verification - and Apple one went without a hitch, the app is already in the store.

    Unfortunately, when I submitted my documents to Google, I've got this message:

    We couldn't verify your ID, so you won't be able to publish apps on Google Play from this account. If you think we've made a mistake, contact Play Console support.

    I thought it was a clear mistake - in the end, I've provided my legit documents - a photo of my driver's licence and a company registration certificate. Surely support will figure it out.

    But upon writing to support I've got this automatic message:

    Unfortunately, we are unable to verify your ID to complete your Play Console registration.

    There was no suggestion to re-submit my documents or provide other documents. After asking multiple questions about how can I resolve the situation, I've got this reply:

    As much as I'd like to help, I'm not able to provide any more information or a better answer to your question.

    Seems like a dead end. I've decided to request a refund and delete my account. But when I asked about it, Google refused:

    Unfortunately, we are unable to provide a refund for the Play Console registration fee if we cannot verify your ID.

    Has anybody seen this before? How did you resolve it? What are my next steps?

    PS. I've seen stories where people were banned from Play Store if they broke rules in their other accounts. I do have another account - my personal one. But I've never had problems with it and it doesn't even have any active apps at the moment.

    TLDR: I worked for months on the app, Google took my money to register a dev account, refused to provide a service using a bogus reason and now refusing to issue a refund. Halp.

    submitted by /u/DontTrustKookaburras
    [link] [comments]

    Speed up your Compose learning by using things you already know from Views

    Posted: 06 Apr 2022 02:20 AM PDT

    Speed up your Compose learning by using things you already know from Views

    It is much easier to use Compose if you know how to do things you already know how to in Views. Let's do a quick jump:

    Before we get started this is the bare minimum you need to know:

    Each component that needs to be rendered on the screen can be defined as a Kotlin Unit function marked with the @Composable annotation like this:

    @Composable fun Article(title: String, description: String) { Card { Column { Text(title) Spacer(Modifier.height(10.dp)) Text(description) } } }

    We call those functions composables. The above composable will render a Card with a title and a subtitle, with a spacing of 10.dpin between.

    Every time the title and description change, the UI will be updated to reflect the updated values. This is what we call recomposition.

    ​

    Set listeners and other common attributes using Modifiers

    There are no setListener() or setPadding() anymore. That's because composables accept the values they need to render on the screen (such as text) as parameters.

    Common attribute such as listeners, elevation, alpha, are passed to composables through a concept called Modifiers.

    There are Modifiers for things like:

    🔹 sizing (size().size(androidx.compose.ui.unit.Dp)), heightIn().heightIn(androidx.compose.ui.unit.Dp,androidx.compose.ui.unit.Dp)) , padding().padding(androidx.compose.ui.unit.Dp,androidx.compose.ui.unit.Dp,androidx.compose.ui.unit.Dp,androidx.compose.ui.unit.Dp)))🔹 functionality (clickable().clickable(kotlin.Boolean,kotlin.String,androidx.compose.ui.semantics.Role,kotlin.Function0)), draggable().draggable(androidx.compose.foundation.gestures.DraggableState,androidx.compose.foundation.gestures.Orientation,kotlin.Boolean,androidx.compose.foundation.interaction.MutableInteractionSource,kotlin.Boolean,kotlin.coroutines.SuspendFunction2,kotlin.coroutines.SuspendFunction2,kotlin.Boolean)), toggleable().toggleable(kotlin.Boolean,kotlin.Boolean,androidx.compose.ui.semantics.Role,kotlin.Function1)), swipeable().swipeable(androidx.compose.material.SwipeableState,kotlin.collections.Map,androidx.compose.foundation.gestures.Orientation,kotlin.Boolean,kotlin.Boolean,androidx.compose.foundation.interaction.MutableInteractionSource,kotlin.Function2,androidx.compose.material.ResistanceConfig,androidx.compose.ui.unit.Dp)))🔹 styling (background().background(androidx.compose.ui.graphics.Color,androidx.compose.ui.graphics.Shape)), border().border(androidx.compose.foundation.BorderStroke,androidx.compose.ui.graphics.Shape)), clip().clip(androidx.compose.ui.graphics.Shape)), shadow().shadow(androidx.compose.ui.unit.Dp,androidx.compose.ui.graphics.Shape,kotlin.Boolean,androidx.compose.ui.graphics.Color,androidx.compose.ui.graphics.Color)), alpha().alpha(kotlin.Float)), animateContentSize().animateContentSize(androidx.compose.animation.core.FiniteAnimationSpec,kotlin.Function2)))

    ​

    From ViewGroups to Rows, Columns and Boxes

    There are no ViewGroups anymore. Instead you can use some specific composables that help you arrange other composables on the screen.

    The most common ones to get started are: Column , Row, Box, LazyColumn and LazyRow.

    Instead of a horizontal LinearLayout, use a Row:

    Row { Text("Main Header") Spacer(Modifier.weight(1f)) Text("23 mins ago") }

    will render:

    https://preview.redd.it/4srtd6hdivr81.png?width=1920&format=png&auto=webp&s=a4bc1937ffa525a4c822aa0a330bc535f9cdea92

    I have added some colored hints on how the composables are layed out on the screen.

    Instead of a FrameLayout, use a Box:

    Box { Image( painter = painterResource(R.drawable.landscape_horizontal), contentDescription = null ) Text( "Preview", modifier = Modifier .padding(4.dp) .clip(RoundedCornerShape(14.dp)) .background(Color.DarkGray) .padding( horizontal = 8.dp, vertical = 4.dp ) .align(Alignment.BottomEnd), color = Color.White ) }

    will render:

    https://preview.redd.it/o5let1auivr81.png?width=1714&format=png&auto=webp&s=5969d7040a8e0ded89a930a6e74950dd8fab9a2b

    Instead of a vertical RecyclerView use a LazyColumn:

    Box { val desertNames = listOf("...") LazyColumn(Modifier.fillMaxSize()) { stickyHeader { Text( "Desert names", modifier = Modifier .fillMaxWidth() .shadow(4.dp) .background(Color.White) .padding( vertical = 20.dp, horizontal = 16.dp ) ) } desertNames.forEach { item -> item { Text( item, modifier = Modifier.padding( vertical = 20.dp, horizontal = 16.dp ) ) } } }

    will render:

    https://preview.redd.it/1a2eiiw1jvr81.png?width=1920&format=png&auto=webp&s=a06489a63a371871970b9dd0ff6810ed7eecacc4

    The final bit you need to know to start using all this is that composable functions can only be used from other composable functions. Because of this, activities that use composables to render their layouts look like this:

    class MyActivity : ComponentActivity() { override fun onCreate(savedInstanceState: Bundle?) { super.onCreate(savedInstanceState) setContent { // use your composables here 🎉 } } }

    Using composables in a Fragment needs a ComposeView like this:

    class MyFragment : Fragment() { override fun onCreateView( inflater: LayoutInflater?, container: ViewGroup?, savedInstanceState: Bundle? ): View? { return ComposeView(requireContext()).apply { setViewCompositionStrategy(ViewCompositionStrategy.DisposeOnViewTreeLifecycleDestroyed) setContent { // use your composables here 🎉 } } } }

    ⚡️ BONUS⚡

    Here is a Cheat Sheet to quickly go through when you need a reminder (right click to save)

    https://preview.redd.it/nz9m65cdjvr81.png?width=764&format=png&auto=webp&s=b0c1182dde78a36cb288c943aad52f22f1296ec3

    submitted by /u/alexstyl
    [link] [comments]

    Android 13 Developer Preview 2 in Emulator

    Posted: 06 Apr 2022 04:18 AM PDT

    Hi. This is the first time that I will be testing an app in a Developer Preview. I noticed in AVD, the API for this preview is Tiramisu and, the target is Android 11.0 (Google Play). Shouldn't it be Android 13.0? Why is this happening? Will I get the real Android 13 developer preview with this?

    Also, which emulator is stable for this to be tested? I tried it with Pixel 4 XL but the app icons are so large.

    Thanks.

    submitted by /u/apprentice4ever
    [link] [comments]

    Private app in the store

    Posted: 06 Apr 2022 02:31 AM PDT

    I'm creating an app for a small company which don't have Google organization and they don't want to buy. I want to distribute my app privately to them through play store. Is it possible to invite them by there gmail or something like this?

    submitted by /u/dugasz1
    [link] [comments]

    Need suggestion for developer accounts & signing certificate.

    Posted: 06 Apr 2022 03:40 AM PDT

    Hey, I have a question regarding having a single certificate for all my applications.

    So I am a newbie RN developer. I am doing a job right now. So the product that I worked on it needs to be pushed to Play Store.

    1. Should I use my google account assigned to me from work to publish the app ?
    2. Should I use my own google developer account for that if my work has no issues with it ?
    3. What if I have to use my work developer account. In that condition can I still sign the app with same certificate which I was using to sign apps from my developer account ?
    submitted by /u/heretostudy219
    [link] [comments]

    Doubt in language update

    Posted: 06 Apr 2022 03:36 AM PDT

    Hey all , I came up with a small doubt related to updating language. As our app provide language change functionality in each and every screen containing articles. As of now we restarting the whole module so that after language updation app goes to the home screen. Instead of that we can set a flag through which we can update when we navigate to the screen. But that requires writing logic in each and every screen which is somewhat complex but achievable. Is there any easy way to update that u have used? kindly mention in the chat.Thank u🙂

    submitted by /u/Employee_Impossible
    [link] [comments]
    Read more
    at

    No comments:

    Post a Comment