we've got an app that's not on the market yet and we are struggling with the testing version that testers download. We're trying to set the v1.0.1 but Google Play redirects them to v1.0.0 which is not up to date. We even tried to deactivate that branch but the issue still insists.
I do a lot of test deployments for multiple test groups.
Google supports 3 separate types of test groups: Open, Closed, Internal.
Open Testing is literally open to anyone who wants to opt in and they can join via a link you can copy from the developer console. Open testing requires the app go thru review before being rolled out.
Closed Testing is similar to Open but you explicitly define who has access with a list of email addresses. Closed testing must also pass through a basic Google review before being rolled out.
Internal Testing is similar to Closed testing but it never goes through a review process. Again, this is controlled via a list of email addresses.
I routinely publish different versions where Internal has the latest bleeding edge.
You don't state which channel you are using (Open, Closed, Internal), but I would carefully review each channel and the email addresses associated. Then I would click on the Publishing Overview button on the console to see if there's something you haven't finished.
Related
I have a functioning Google Sheets Add-on that is listed in the Google Workspace Marketplace. I've made changes in the new Apps Script Editor and tested them locally, now I want to push them to my users.
The process as I understand it, to press "New Deployment"
add a description and press "deploy"
after which I copy the "Deployment ID" into the Google Workspace Marketplace SDK page,
and hit SAVE in the bottom.
It's been a few hours and I still cannot see it being live.
Is there a review process for updates like this? Or am I missing a step?
The previous version is still being served to users as far as I can tell.
Update in response to the comment from #ziganotschka
I am making a Google Sheets Editor Addon, and I'm only now understanding the difference between that and the Google Workspace Addon. I've resubmitted my store listing for review with Google Workspace Addon disabled, and removed the "Common" part of my manifest. I've updated the "version" number to correspond to the latest deployment.
Is it not possible to test a Sheets Editor Addon from the new editor without deploying it as a Workspace Addon? And should updating the version number be sufficient to roll out an update?
From the question
Is it not possible to test a Sheets Editor Addon from the new editor without deploying it as a Workspace Addon?
It depends on what kind of test do you want to do, if your Apps Script project is bounded or a standalone project and what do you Editor add-on does and how it does that.
I.E. you might test a simple edit trigger (onEdit) by using a function for mocking the edit event object and passing it to the onEdit function. To be clear this doesn't need to create a new version and for testing and add-on it's not necessary to make a new deployment.
And should updating the version number be sufficient to roll out an update?
It depends on if the Cloud project OAuth consent screen was set for external use or for internal use, in the new version requires new scopes.
Let say that you fixed typo on a variable name, in this case only creating a new version and adding the version number to the add-on configuration page will be enough, but if you added a sensitive API and you add-on is set for external use, then you will have to update the OAuth consent screen and wait for Google review and approval.
I successfully developed an application through BLPAPI (Bloomberg API) on a Bloomberg Terminal machine (in Python). Unfortunately my company is thinking to switch to Bloomberg Anywhere...I will have the chance to run my application there?
With a move to Bloomberg Anywhere from open Bloomberg, you will have the same access to data that you had before. However, you will need to keep the following in mind:
Authentication will be linked to an individual person instead of a Username/Password. This means that the person who owns the Bloomberg login will need to be physically present at the machine to login using their fingerprint on the Bloomberg keyboard, a b-unit, or our newly released b-unit mobile app (for recent versions of android).
Your app will no longer be limited to running on the current machine only. You will now be able to install a Bloomberg access point and use your application on any windows machine as long as you have the person present as described above to log into the box.
Once logged in you will have data access for a few days, however if the Bloomberg anywhere user logs in to Bloomberg on a separate machine, then the machine with your python application will immediately lose access to data. To regain access, the Bloomberg anywhere user will have to re-login to the original machine.
hope this helps
Yes. Just be sure that the user logs in every so often. The API will work when a user is connected and even after they disconnect, for a while.
Yes, it should work fine, we've done some applications under BBanywhere.
The only issue I've seen which you should contemplate before going live application is ensuring that if you're moving it off the main box and it's a non-technical party using the service on a laptop or something, that the appropriate python install and dependencies are set up (ie. conda, blpapi, etc.) I've seen some people comfortable enough to run the script or app, then run on laptop or other computer under anywhere all of a sudden that doesn't work because the dependencies aren't there.
We are in the process of implementing Success Factors LMS, and trying to play and view SCORM compatible files exported from Adobe Captivate 8 and 9 in Success Factors LMS.
I get the message - 'ERROR – unable to acquire LMS API, content may not play properly and results may not be recorded. Please contact technical support’
I have tried SCORM versions 1.2 v3 and 2004 V2 and V4. We can view the content, however it does not track, show as complete etc.
We are also producing Scorm compliant files using Skillcast and Articulate, but we still hit the same issue, we can view the content after closing the API error window, but still does not track.
Anyone experienced this problem before? Or know of a fix?
Many thanks
Normally this issue comes up when the course is unable to get the SCORM API from the LMS...I have seen a ton of SCORM content running in Success Factors before, so I wonder if the issue is in the setup. Are you seeing any "Access Denied" type errors in the browser element inspector/developer tools? I wonder if the course just can not find/have access to the player window. If the course is launching in a new window, you may want to try launching it in the frameset. I have seen folks get around this issue by making sure the player and sco are in the same window...
If you wanted to rule out the content being the issue, you can always test your content in the SCORM Cloud's free sandbox (https://cloud.scorm.com) to make sure the course is properly asking for the API...
If you have any other questions, we would be happy to help...you can just shoot us an email at support#scorm.com.
Thank you!
Joe
The error occurs because the content is not speaking to the Learning Management System (LMS). The code that runs to initialize the session doesn't happen. There is no return "ping" from the LMS.
You will get this error when you publish in SCORM and run from your desktop, or from a web server that isn't connected to an LMS. If it occurs when you are launching from an LMS it can either mean that the SCORM API isn't configured correctly, or your content server is on a different domain (cross-domain) than your application servers.
To test, you should try launching your content in different browsers. Our system was configured in such a way that Firefox and Chrome read our content to be cross-domain issue, and threw the SCORM API error, but Internet Explorer worked just fine.
In the end, it was determined that our server configuration in tandem with our firewall and security settings read the Content server as cross-domain and we had to redeploy our content servers within the firewall.
iTunes Connect - Prerelease - Beta testing with Internal testers says 31 days left, what does this mean?
Will the app uninstall itself after 30 days? Will it become inactive or unusable? What happens?
From some months' experience, I find that my original answer(guess) is not right. If an application has expired on iTunes Connect Beta Testing. It will very soon(in one or two days after the expiration) stop working from the device that has it installed.
Original answer:
Short answer: when the testing period end, testers will no longer be able to accept invites and install builds. Testers that already have builds installed will not be affected.
In this document,
https://developer.apple.com/library/ios/documentation/LanguagesUtilities/Conceptual/iTunesConnect_Guide/Chapters/BetaTestingTheApp.html#//apple_ref/doc/uid/TP40011225-CH35-SW2
Apple says:
“After the 30 day testing period has ended, the build status changes to Expired"
"To continue testing after the 30-day period expires, upload another build. Internal testers will automatically receive an update notification when the new build is available. To distribute the new build to external testers, you must submit it to Beta App Review. Once it is approved, you can send the external testers an update email by clicking Send Invites from the External Testers column on Builds, as shown above."
Apple doesn't describe clearly the behaviors on the tester side when a build expired.
But when I try to turn off the "TestFlight Beta Testing" on an app,
the prompt says:
"Are you sure you want to stop testing?
Testers will no longer be able to accept invites and install builds. Testers that already have builds installed will not be affected."
So I guess the behaviors on the tester side when a build expired are going to be the same
as that when the testing is shut down by turning off the "TestFlight Beta Testing" option.
In my experience with Internal testing, after 30 days, the build changes to Expired, and will no longer launch on devices where it has already been installed. Trying to launch the app will show the splash screen, and then it immediately quits and you're back on the home screen.
I've also found that uploading a new build does NOT automatically send out the update to existing internal testers. Although iTunes Connect will say the build is available, you have to manually toggle TestFlight testing off and then on again to get it to recognize the new build and send out the update emails to existing internal testers.
Here's what I want to be able to do:
Run a program on my local computer which logs in to a citrix server (using citrix receiver or doing so in a similar way), on the server in the citrix session open a web browser, load a website, and then bring the html of that site back out of the citrix session and onto my local computer. Bascially I want to get data out of a citrix remote session.
How can I do this programmatically?
I'm fine with whatever programming language/modality you are comfortable in answering the question using.
I've looked a little into the citrix apis but while I find some things about logging in and even sending keystrokes and mouse clicks I found nothing about obtaining data. I could just log in and then use a program like wireshark to get the information, but I'm guessing it's all encrypted (plus then I wouldn't be doing my task all programmatically). I know of at least one open source program which seems to be able to replace a citrix reciever/client (openthinclient.org) but before I got digging through all its source code to try to answer my question I thought I'd ask here in case someone had an easier answer.
If all you want is to automate the task, is having the program act as a citrix client necessary?
I assume you don't have install privileges inside your citrix session, so are unable to install one of the many automation tools available (such as http://docs.seleniumhq.org/)?
Given the above...
If you have/allow java on your local machine, have a look at http://www.sikuli.org/
The main difference between this and other automation tools I've come across is that Sikuli uses the image on screen to navigate the gui, rather than grabbing calls to the widgets (which wont work in a citrix session).
So, assuming you can take a screenshot of your citrix session, it could be useful to you.