Im trying to figure out how DVCS Connector plugin works. Im trying to link my commits to Jira issues.
As far as I can tell it seems like my setup is correct. At least it doesnt complain about anything.
I add my issue to the comment like "MBL-10 Fixed some minor issues with.." but they are not linked with the issue.
When I try to push the "Force Sync" button it say "Last commit 7 hours ago" and it's beein saying that the entire day.
Anyone bumped into similar problems before?
Btw, Im using Jira OnDemand.
Related
Im having issues entering Utgarde pinnacle and ToC 5 man.
Running straight into the portal triggers no teleport, however if I strafe into the portal it triggers with 100% success.
I cant find anything relating to this problem. And i have no idea where to look for a cause.
Any help to point me in the right direction will be much appreciated
This is how my Utgarde pinnacle portal looks in the SQL.
(heroic portal highlighted)
Updating Azerothcore repository on the server, recompiling and then importing updates fixed the issue.
Whenever I try to create a new Audience for my ios app on Firebase I get the error : " Cannot be created due to a server error". No matter the parameters I include.
A week ago it was working correctly,I have tested from other computers on the same project.
I only have one project, so I Cannot test on other projects.
Thanks lots
The issue with audience creation is a known bug.
The engineers are already looking for possible solutions to fix it.
Update: Got an e-mail this morning that it should be fixed now. Checked it and it's working again for me.
Just checked and looks as already fixed. Seems to be working correctly.
I've been working on a game using Google VR in Unity3d and I recently updated my version of unity3d and the (built in) Google VR SDK to the latest version. After doing so the pre-launch report (automated testing on firebase) is showing crashes, during the unity splash screen, on 5 out of 6 devices.
This is the issue that is reported:
Issue: Crash of app uk.co.softkitty.puzzleroom running instrumentation ComponentInfo{com.google.android.apps.mtaas.crawler/android.support.test.runner.AndroidJUnitRunner}
Not very helpful, it looks like a generic unit test result if the app closes unexpectedly . I've looked through the logs and cant find anything unusual from my app or unity, but I did find something. It looks to me like this may be being caused by the test script itself:
10-27 01:54:54.494: I/ViewInteraction(19677): Performing 'single click' action on view (with class name: is "android.widget.ImageButton" and with id: uk.co.softkitty.puzzleroom:id/ui_back_button ...............
This to me, looks like the test runner is exploring the app UI and the first thing it does is click the "back" button. Which I would expect to close the app. I also tried using Firebase directly, which seemed to confirm it:
Firebase Activity Map
Does that seem likely that this is just a bug/red herring caused by changes to unity/GVR Or even firebase? Has anyone else experienced this?
I just don't want to release it if it really is crashing on so many devices!
Many Thanks
I asked Google Play Support about this and they got back to me.
They have confirmed that the issue is caused by a new crawler used by the Pre-Launch report. Details can be found here under the section "Pre-launch report versions"
They've escalated the issue and have also provided a workaround:
Sign in to your Play Console.
Select an app.
Select Release management > Pre-launch report > Settings.
In the “Pre-launch report version” section, move the Opt-out switch
to the right until it turns blue.
I haven't verified this yet but will mark as answer once I have.
Edit
I have tested this and all the tests pass again so this looks like a good solution for now.
We got this when uploading our APK as well. It started October 27th and crashed the following 4 days until we changed our setup. I couldn't see anything in our code base that should trigger this problem, so I wonder if it's related to changes on Google's side.
However, we did just did two changes and now everything's working again.
We added the following line to proguard-project.txt:
-keep class android.arch.** { *; }
I assume this was what fixed it.
At the same time we changed the compileSdkVersion and targetSdkVersion to 27 (and correspondingly all belonging support libs). For all I know they could have fixed it here too..
Edit:
To more directly answer your question: Yes, it does seem likely that this is just a bug/red herring, not on Unity's side, but in Firebase Test Lab or in Google's support lib. I tested the APK that failed the pre-launch tests and it worked just fine on my device.
WEIRD HAPPENING.. I am unable to debug meteor app , BREAKPOINTS doesn't work in chrome(can see the server side sources thou).. I have already wasted 2 days over it ..
I have already tried
Meteor: Debug on server side
Also tried similar options changing web-port and other options.
Also tried to reduce the node-inspector version, BUT breakpoints are not working for me..
any suggestions on how to debug this issue?
(Chrome browser, ubuntu, AMD machine, if that matters)
I have the same issue. The only workaround I've found is to put debugger; statements in my code. Those are respected and treated as breakpoints which stop the server for Node Inspector.
you can try observatory or read this article, maybe it'll helps
You are not alone. There is an issue posted to github about this, and it appears to be confirmed by several users.
I was able to get Node Inspector to work a while ago by downgrading to 1.10. It's not as nice as the new version but worked last time I used it. I honestly haven't needed it recently, but hopefully it'll still work.
hello guys I am uploading an app to google play for the first time and using a tutorial to test OBB downloading . while everything up until this point has worked like a charm so far the one issue and step i missed was activating an apk on google play. it looks like it should be as simple as a button but i don't see where exactly I should be disabling or enabling the option on the developer console .
when i look for how others do it their consoles always look different from mine so am i even approaching this in the right place ? could there be a reason this option is hidden ?
here is a picture of where I am looking for this option on my console but i'm just not seeing it. any and all help is appreciated. it would be nice if i am just being blind and overlooking it or looking in the wrong place versus this being an error with my uploading the .apk