Fabric Beta: Tester device ID does not appear after accepting invite - google-fabric

I've sent several invites to a tester, and he has accepted them on his iPhone 6s, but the device ID does not appear in Fabric. Here's what appears when I view the user:
Screenshot of user profile in Fabric
As you can see the iPhone 6s appears under "devices" but the top tab still reads "0 devices" and the UUID cannot be found anywhere. Am I missing something? Is there some reason why his device might be failing to send the UUID?

Related

OAuth on iPhone XR 2020, iOS 14.7.1 unexpected behavior in username entry

When connecting to Google to integrate Nest into another system (in this case Flair Systems) on an iPhone XR 2020 running iOS 14.7.1, the following happens:
I click the link in the Flair App to connect to Google Nest
I am directed to a standard Google OAuth portal
I enter a username with a Google Nest account associated with it
I click the Next button
The gray placeholder text "Email or phone" reappears, overlaid on top of the email address I just entered. The part of the email address that extends beyond "Email or phone" remains visible
The expectation is that I would instead be asked for a password, or informed that the user account does not exist. Image of faulty login state
There is little we can do to attempt to repair or circumvent this from our side. We have seen this in other users on iOS devices as well.

How to customize the main store listing in the google console?

I have question is their way to customize the main store listing? I want to remove the table requirements because the app want to apply on the phone devices not in the tablet devices.
I read some articles or post that I need to go this section in the google console.
Reach and devices -> Device Catalog
You can limit your app to Phones only from the app manifest for more on this see this answer.
for Google Play store listing, you can add 1 screenshot for each tablet size using a phone screen shot, in that way you will only target phones.
the problem with "Device Catalog" approach that you will need to do this every time new devices were added to google play console which is very hard to do.

safari 13.1 navigator.mediaDevices.enumerateDevices() return only audio devices

Im facing with an issue on desktop Safari 13.1 version. If I open the console in the web inspector (with a regular macbook which has webcam and mic) and execute this command on any kind of website:
navigator.mediaDevices.enumerateDevices()
First time it will return in the Promise result with a videoinput and an audioinput.
Second time it will return only 2 audioinput. Videoinput is disappear.
Unfortunately I call this method several times while checking the available devices on my solution.
Any idea why does it happen and how could I get the accurate information about the devices even If I call it more than once?
See the results here
I've found the same issue, also on my iPad running iOS 13.
It seems you need to request camera access first in order to see the correct device list.
navigator.mediaDevices.getUserMedia({ video: true })
This will prompt you for access to the camera (you need to be on HTTPS or localhost).
Grant permission, then run this again and you should see the videoinput device(s) listed in the returned promise:
navigator.mediaDevices.enumerateDevices()
I guess this makes sense as a privacy feature that a website cannot check if a camera exists without first asking your permission.

Notification text in android is not shown completely

I am new to push notifications in IBM mobile first Hybrid platform. I am able to send push notifications to all devices. However, in android devices I'm not able to see the complete message; only half of the message is shown. Please suggest answers.
just change the character settings from medium to small
settings > character > small

Unusable UDID in new ios7 (with FFFFFFFF prefix)

I need to register new device because I need mobileprovision. I can't use mobileprovision because UDID has FFFFFFFF on start. I think it is wrong UDID.
Any idea how to fix it?
Yes. The "FFFFFFFF" UDIDs are wrong. This seems due to the fact that the UDID is now considered a Privacy Topic and thus Apps are not allowed anymore to retrieve them... and iOS returns an obfuscated UDID if called and precedes the first digits with FFFFFFFF. So I guess some of your clients got the UDID via an App on the device.
See here: https://stackoverflow.com/a/19032885/2580805
"The only & unique method to get UDID under iOS7 is to plug your device to a computer, launch iTunes (or Xcode) and copy the displayed UDID."
But I have to add: there are at least two more options:
Our testers that provided their UDID by registering their devices via TestFlightApp.com also got non-FFFFFFFF UDIDs that worked.
Testers can surf with their device's Safari to: http://udid.io - this site installs a (temporary!) profile on the device which allows it to show the user a working UDID for copy & paste.
you can use to get the proper UDID of the device(s) the followings:
iTunes application;
the Xcode Organiser option;
or online:
http://get.udid.io (the actual device needs to open this site);
get UDID through Organizer or iTunes. if you are getting it through 3rd party software, that might be wrong.
For Organizer, press Command+Shift+2 on XCode
You can avoid installing iTunes on Windows by using USBDeview, which is less than 200k in size. The "Serial Number" column under USBDeview is the UDID.