Too Few Items in Teams

XCode Too few items in teams error when refreshing provisioning profiles

It seems like I had two accounts for apple like most people: 1) email address account and 2) just apple user ID login.

When you sign up for an iOS developer account, only one account gets approved as an iOS developer. It doesn't matter if those two accounts are merged and linked inside apple profile, only one gets approved. You can check this by logging into both accounts separately to their developer website. One account will say you are a member and another will say pay up the fee to become iOS developer.

The problem is that your keychain already stored one of apple id credentials from the past... and you probably signed up for apple iOS developer program using the other apple login. Xcode automatically gets keychain's previously stored credential for 'Teams' section and since that account from keychain was not activated for the iOS developer account, it's complaining that no one is a valid developer in 'Teams'.

To solve this,

1. delete any, all apple related stuff from your keychain login.

2. revoke all the problematic profiles, certs, etc from apple website.

3. just redo provisioning process only using iOS developer approved apple login.

4. From XCode Organizer's Teams section, click 'refresh' icon at the bottom and follow direction.

Too few items for RecyclerView on screen

Android has this Paging Library now which is about displaying chunks of data and fetching more when needed. I haven't used it and it looks like it might be a bit of work, but maybe it's worth a look?

Codepath has a tutorial on using it and I think their stuff is pretty good and easy to follow, so maybe check that out too. They also have this older tutorial that's closer to what you're doing (handling it yourself) so there's that too.

I guess in general, you'd want your adapter to return an "infinite" number for getItemCount() (like Integer.MAX_VALUE). And then in your onBindViewHolder(holder, position) method you'd either set the item at position, or if you don't have that item yet you load in the next page until you get it.

That way your initial page will always have the right amount of content, because it will be full of ViewHolders that have asked for data - if there's more than 10, then item 11 will have triggered the API call. But actually handling the callback and all the updating is the tricky part! If you have that working already then great, but it's what the Paging library was built to take care of for you (or at least make it easier!)

Related Topics