The Fabric beta manual distribution sometime does not send invitation email even in the webpage it show "Invited" to the person. If I click resend invitation, that person will get it. My QA team people has to come to me all the time for resend the invitation. I know Fabric team always around here so My question is : Is it a known issue and Do you have solution or workaround for it?
Mike from Fabric here. Invitations are sent once per tester per app. If a tester doesn't accept the original email, then additional invites will only be sent if you resend the invite to them and they won't receive notices of new builds since they're not testing the app.
Beacause if tester doesn't accept the first invite email, the next invite emails will not be sent.
Trick for resent invitation: if tester's email is gmail, add surffix to tester's email, ex:
tester#gmail.com -> tester+1#gmail.com
Invites are sent once per tester app as Mike mentioned above. If a tester does not accept the initial invite or had unsubscribed then tester will not receive the email, but the developer can resend an invitation in the Beta dashboard (see beat dashboard image) and the tester should get that invite. If tester still not getting the invite then reach out to Fabric support (to unblock/re-subscribe the tester) or ask developer to resubscribe from the initial/first invite.Beta dashboard image
Related
I'm developing an iOS app for a client. I attempt to add him as a user under "Users and Access" using his apple ID email address. He receives the invite and enters his apple ID and password, but receives this error message:
"Unable to Sign In" - "This app is used by developers to manage apps on the App Store. To get access, ask your Account Holder to set up an App Store Connect account for you. (2002)"
Under Users and Access, the user record is grayed out as though he hasn't accepted the invitation, and I can't add him as a tester in the app yet.
For anyone facing this issue:
I faced the same problem today, deleting the invitation and sending it again worked.
FYI: First I had sent an invitation with the role "Developer" and later with the role "Admin", which might have had something to do with it working
just remove the invite and do it again, it is better if the team is coordinated and understands how the aggregation process works
I came across a newsletter in which they have a WhatsApp link and when i click on it i am able send predefined message to predefined number.
SEND INQUIRY VIA WHATSAPP button is linked to below for example
https://whatsapp://send?phone=XXXXXXXX&text=Hi%2C%20this%20is%20test%20message.
Can i use this link in my newsletter without any restriction as i have a database of 2000 subscribers...
or i have to use some sort of verified mechanism using API so that whatsapp is not abused.
This link seems to be vulnerable and can be used for spam or its fine to use it
your URL is basically mal-formed.
The whatsapp:// is a kind-of protocol for transmitting information, and what you can do is to add it to a webpage as a link, so the visitor, upon clicking on that link from their phone, can access directly to Whatsapp.
Remember the oldie-goldie mailto:// which allow visitors to directly open the mail client they have on their computer, and pre-fill some email fields? This is the same.
Here is a really simple code-pen showing how can this be achieved.
Be sure to visit the codepen from your mobile:
https://codepen.io/diereysaa/pen/QWbjXGW
Replying to your specific question, there's no limitation on the use of this, since the executor will be each one of your subscribers, not your webserver. The only limitation will be your own phone, because if all of those 2,000 subscribers reply using the whatsapp link... you'll get 2,000 messages :D
I need some assistance understanding an aspect of this function provided by fabric
As far as I understand by setting:
ext.betaDistributionGroupAliases = "testers"
When the APK is uploaded, those members of that testers group should receive an email invitation to test.
This is not the case in my instance.
The APK does upload and the users are associated with this build as can be seen by the console (it says 9 invited). But no emails are actually sent out.
I would prefer to use the group alias as this saves me having to manage email addresses in the gradle file.
What am I not understanding?
Mike from Fabric here. There's a couple of different reasons why you're testers wouldn't be notified.
1) If you have the following set, then testers would not be notified:
ext.betaDistributionNotifications=false
2) If a tester was invited, but never accepted the original invite, they won't be notified of new builds since they are not testing.
3) If the build and version number of the build are the same and you are re-distributing the build, then only new testers would be notified.
4) If the tester unsubscribed to update from Beta about app updates, then they won't be notified.
5) If for some reason a tester's address is invalid, then our mail server may have a bounce for their email address. If you think that this is happening, then emailing the Fabric support team at support(at)fabric(dot)io would be your best bet.
6) The tester could be getting the email, but not seeing it and it could be in a spam or junk folder.
I am trying to create a MySpace API so that my users can connect to my site using MySpace.
All the tutorials say "go to http://developer.myspace.com/ and create a developer account..."
I signed up for a new MySpace account, verified my email, gave them access to my gmail so they could search for friends, invited a few friends, basically completed all the steps they ask you too as a new user...
But whenever I go over to http://developer.myspace.com/ and click "Developer Sign Up" or "Start building!" I receive an error message that says:
We're sorry, but you must verify your email address first! You cannot access many MySpace features until you complete this step. Please return to your MySpace profile and click the "Verify your email address" link. When this step is complete, you can re-apply to the developer platform.
I have verified my account 3 times using the link in the email they sent me, and waited 24 hours for any changes to be applied. There is no "Verify your email address" link on your profile page, so this appears to be a deprecated error message.
A bit of digging around shows this problem has existed since at least 2 years:
http://developer.myspace.com/community/forums/t/9579.aspx?PageIndex=1
... and has even been posted on here, without resolution: Myspace developer api: No access / verify email
Any ideas how to get access to my API key?
Do I just have to wait for my account to show as verified...? (It's been 24 hrs already)
I am working on an app in iTunes connect for a client, under their iTunes connect account. I want to add myself as a user so that I can get email notifications of updates in app status. When I try to add myself as a user I get the following message:
The email address you entered already belongs to an iTunes Connect account. To continue, enter a different email address
I am using this email address on my own company's iTunes connect account, but not on my client's account. How can I add myself as a user?
#sarnold Turning your comment into an answer because it worked for me.
Two Separate Websites
Apparently for historical and organizational reasons, Apple operates their developer and app store business in a bifurcated manner.
developer.apple.com
The web site for all the technical resources, including documentation, WWDC videos and such.
itunesconnect.apple.com
This completely separate web site handles the business end:
Contracts, banking, payments.
Uploading your finished app.
Defining your In-App Purchase products.
Problem: Different Handling Of Accounts
The developer.apple.com site is slick in that a programmer can have a single Apple ID used to join multiple developer accounts. She may work for three different companies, and be assigned a role on each of those companies’ Developer accounts all on the same Apple ID. When she logs in to the Developer site, she is presented with a popup menu asking which of the three companies’ Developer accounts she wants to access during this work session. Nice.
The problem: in iTunesConnect, not so nice. In iTunesConnect, the "admin" person cannot assign existing Apple IDs as members with a role. Very strange. The admin is forced to create a new ID for each person being adding to the team. That means the person joining must have multiple email address. If an admin tries to add you to their iTunesConnect with an email address already used on some other company's iTunesAccount, an error message reports that email address / Apple ID is already in use. Obviously the programming team running the iTunesConnect site could use some help from the Developer site's team. ☹
Workaround: Email Address Trick
The workaround cited by sarnold involves a feature of email addresses. The spec for email servers has a feature where you can extend your email address. You can add a suffix to the first part of your email name by appending a "+" PLUS SIGN. From what I could figure out, the email software first looks for the extended name. If no such name is found, it drops the extension and looks again. If found, the shorter version of the email address is actually used.
So if the programmer Susan wants to use her email address susan#example.com for a second or third iTunesAccount, she tells her client's admin person at Acme Corporation to use something like this as her email address: susan+acme.com#example.com. Apple will still create a needless extra Apple ID for Susan, but at least Susan does not have to bother with creating and accessing extra email accounts. The emails sent by Apple will arrive at her susan#example.com address.
Susan double-checked this would work before talking to the admin person. She sent herself an email to susan+acme.com#example.com to make sure it arrived at the susan#example.com account.
Effectively, the email servers are not fooled by the extended email address, but iTunesConnect is fooled into creating an new Apple ID using an old email account.
Basically, you can't invite other iOS devs to review your efforts seems to be the result of this policy.
I had (and have) the exact same problem... what makes me kinda like FlavorScape's suggestion ;)
What I did is something similar to sarnold's comment: I used an alternative email address (_#gmail.com instead of _#googlemail.com) and this actually created a new AppleID with this email address.
It works fine, but it would be so much better to just connect my actual Developer account to my client's.
The way it's like at the moment, I can not even access the developer resources and (most importantly) the provisioning center with the new Apple ID, so my client has to do create new provisioning profiles and stuff, which is pretty frustrating and complicated.
Additionally, it is a pain to let him test the Apps on his own devices, because of the developer certificate is installed on my Mac, not his, and I am therefore the only one (or better, my Mac is the only computer) that can install new provisioning profiles on his devices.
Is there a better way to connect the accounts and solve these problems?
Cheers,
Nils
Apple now will allow the same email address to be invited to multiple itunes connect accounts and no longer allows new emails to be added with the +. Just a word of warning to others who were doing this the original post is now out of date with Apples new policy it seems.
#knl: The problem in the original question is specifically with iTunes Connect. If you want to be able to manage the Provisioning center -- to make profiles etc -- ask your client to add you to that account. Here are the steps:
Go to "Member Center"
Select the "People" tab
Click on invitations
Select "Invite person"
in the next screen they can select your role including "Member" (limited access) and "Admin" (full access)
From apple documentation:
You can only create test user accounts using an iTunes Connect
accounts with the Admin or Technical role assigned to it. Test users
do not have access to iTunes Connect, but will be able to test in-app
purchases in a development environment on a registered test device.
Link here