Missing version in Fabric Crashlytics
Everytime I release a new version of an app, this version shows up in Fabric crashlytics service, and I can track crashes, non-fatals, etc.
My issue is that I released a version on monday (11/19/18) but the version number is not showing up in crashes version filter. The next version (not on the store yet, but on testflight) is showing tho.
I have no idea how this is possible, if it comes from changes in fabric/firebase, or if it's coming from me (I don't see a thing I did differently than usual).
I will take any hint, help, and similar cases from you guys.
I know this is not a question strictly about development but the forum button on fabric website redirect to SO.
ios swift crashlytics google-fabric
asked Nov 19 '18 at 17:08
Damien BannerotDamien Bannerot
2,35411121
add a comment |
Everytime I release a new version of an app, this version shows up in Fabric crashlytics service, and I can track crashes, non-fatals, etc.
My issue is that I released a version on monday (11/19/18) but the version number is not showing up in crashes version filter. The next version (not on the store yet, but on testflight) is showing tho.
I have no idea how this is possible, if it comes from changes in fabric/firebase, or if it's coming from me (I don't see a thing I did differently than usual).
I will take any hint, help, and similar cases from you guys.
I know this is not a question strictly about development but the forum button on fabric website redirect to SO.
ios swift crashlytics google-fabric
asked Nov 19 '18 at 17:08
Damien BannerotDamien Bannerot
2,35411121
I have the opposite - new version number immediately in the filter but no crash reports...
– Ewan
Nov 20 '18 at 20:57
@Ewan maybe you haven't had any crashes for that version? Try forcing one and see if it shows up (see Crashlytics Docs)
– KevinTydlacka
Jan 1 at 18:11
@Kevin - my big problem was releasing using './gradlew installRelease' rather than 'Build > Generate signed....' in AS. All working now stackoverflow.com/questions/53420776/…
– Ewan
Jan 2 at 18:25
add a comment |
Everytime I release a new version of an app, this version shows up in Fabric crashlytics service, and I can track crashes, non-fatals, etc.
My issue is that I released a version on monday (11/19/18) but the version number is not showing up in crashes version filter. The next version (not on the store yet, but on testflight) is showing tho.
I have no idea how this is possible, if it comes from changes in fabric/firebase, or if it's coming from me (I don't see a thing I did differently than usual).
I will take any hint, help, and similar cases from you guys.
I know this is not a question strictly about development but the forum button on fabric website redirect to SO.
ios swift crashlytics google-fabric
asked Nov 19 '18 at 17:08
Damien BannerotDamien Bannerot
2,35411121
Everytime I release a new version of an app, this version shows up in Fabric crashlytics service, and I can track crashes, non-fatals, etc.
My issue is that I released a version on monday (11/19/18) but the version number is not showing up in crashes version filter. The next version (not on the store yet, but on testflight) is showing tho.
I have no idea how this is possible, if it comes from changes in fabric/firebase, or if it's coming from me (I don't see a thing I did differently than usual).
I will take any hint, help, and similar cases from you guys.
I know this is not a question strictly about development but the forum button on fabric website redirect to SO.
ios swift crashlytics google-fabric
ios swift crashlytics google-fabric
asked Nov 19 '18 at 17:08
Damien BannerotDamien Bannerot
2,35411121
asked Nov 19 '18 at 17:08
Damien BannerotDamien Bannerot
2,35411121
asked Nov 19 '18 at 17:08
Damien BannerotDamien Bannerot
2,35411121
asked Nov 19 '18 at 17:08
Damien BannerotDamien Bannerot
2,35411121
asked Nov 19 '18 at 17:08
Damien BannerotDamien Bannerot
2,35411121
2,35411121
I have the opposite - new version number immediately in the filter but no crash reports...
– Ewan
Nov 20 '18 at 20:57
@Ewan maybe you haven't had any crashes for that version? Try forcing one and see if it shows up (see Crashlytics Docs)
– KevinTydlacka
Jan 1 at 18:11
@Kevin - my big problem was releasing using './gradlew installRelease' rather than 'Build > Generate signed....' in AS. All working now stackoverflow.com/questions/53420776/…
– Ewan
Jan 2 at 18:25
add a comment |
I have the opposite - new version number immediately in the filter but no crash reports...
– Ewan
Nov 20 '18 at 20:57
@Ewan maybe you haven't had any crashes for that version? Try forcing one and see if it shows up (see Crashlytics Docs)
– KevinTydlacka
Jan 1 at 18:11
@Kevin - my big problem was releasing using './gradlew installRelease' rather than 'Build > Generate signed....' in AS. All working now stackoverflow.com/questions/53420776/…
– Ewan
Jan 2 at 18:25
I have the opposite - new version number immediately in the filter but no crash reports...
– Ewan
Nov 20 '18 at 20:57
I have the opposite - new version number immediately in the filter but no crash reports...
– Ewan
Nov 20 '18 at 20:57
@Ewan maybe you haven't had any crashes for that version? Try forcing one and see if it shows up (see Crashlytics Docs)
– KevinTydlacka
Jan 1 at 18:11
@Ewan maybe you haven't had any crashes for that version? Try forcing one and see if it shows up (see Crashlytics Docs)
– KevinTydlacka
Jan 1 at 18:11
@Kevin - my big problem was releasing using './gradlew installRelease' rather than 'Build > Generate signed....' in AS. All working now stackoverflow.com/questions/53420776/…
– Ewan
Jan 2 at 18:25
@Kevin - my big problem was releasing using './gradlew installRelease' rather than 'Build > Generate signed....' in AS. All working now stackoverflow.com/questions/53420776/…
– Ewan
Jan 2 at 18:25
add a comment |
2 Answers
2
active
oldest
votes
So, after some digging and help from Firebase/Fabric people, I've resolved this issue.
It appears that I had too many active versions for my app, Crashlytics was tracking too many versions and couldn't show some more.
After removing a few outdated versions, everything came back to normal and all the data were there retroactively.
I hope this post can be helpful for some people, I didn't manage to find any informations about that problem. It might be useful to put that piece of information in Fabric documentation.
answered Nov 21 '18 at 10:08
Damien BannerotDamien Bannerot
2,35411121
add a comment |
For me the solution was different.
The app I was updating had previously used Fabric Crashlytics. When updating the app I converted the integration over to the Firebase Crashlytics integration (deleted the API keys from the build script, removed the Fabric with statement in the App Delegate, etc.)
I confirmed with Crashlytics support that if you are updating an app that was initially integrated with Crashlytics using the Fabric docs then you must continue to use that integration even if you have connected your app to Firebase and now use Firebase.
I pushed an update out where I reverted back to the integration outlined in the Fabric docs, and I now have Crashlytics data for this version in Firebase and Fabric.
answered Jan 1 at 18:08
KevinTydlackaKevinTydlacka
4211919
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53379543%2fmissing-version-in-fabric-crashlytics%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
So, after some digging and help from Firebase/Fabric people, I've resolved this issue.
It appears that I had too many active versions for my app, Crashlytics was tracking too many versions and couldn't show some more.
After removing a few outdated versions, everything came back to normal and all the data were there retroactively.
I hope this post can be helpful for some people, I didn't manage to find any informations about that problem. It might be useful to put that piece of information in Fabric documentation.
answered Nov 21 '18 at 10:08
Damien BannerotDamien Bannerot
2,35411121
add a comment |
So, after some digging and help from Firebase/Fabric people, I've resolved this issue.
It appears that I had too many active versions for my app, Crashlytics was tracking too many versions and couldn't show some more.
After removing a few outdated versions, everything came back to normal and all the data were there retroactively.
I hope this post can be helpful for some people, I didn't manage to find any informations about that problem. It might be useful to put that piece of information in Fabric documentation.
answered Nov 21 '18 at 10:08
Damien BannerotDamien Bannerot
2,35411121
add a comment |
So, after some digging and help from Firebase/Fabric people, I've resolved this issue.
It appears that I had too many active versions for my app, Crashlytics was tracking too many versions and couldn't show some more.
After removing a few outdated versions, everything came back to normal and all the data were there retroactively.
I hope this post can be helpful for some people, I didn't manage to find any informations about that problem. It might be useful to put that piece of information in Fabric documentation.
answered Nov 21 '18 at 10:08
Damien BannerotDamien Bannerot
2,35411121
So, after some digging and help from Firebase/Fabric people, I've resolved this issue.
It appears that I had too many active versions for my app, Crashlytics was tracking too many versions and couldn't show some more.
After removing a few outdated versions, everything came back to normal and all the data were there retroactively.
I hope this post can be helpful for some people, I didn't manage to find any informations about that problem. It might be useful to put that piece of information in Fabric documentation.
answered Nov 21 '18 at 10:08
Damien BannerotDamien Bannerot
2,35411121
answered Nov 21 '18 at 10:08
Damien BannerotDamien Bannerot
2,35411121
answered Nov 21 '18 at 10:08
Damien BannerotDamien Bannerot
2,35411121
answered Nov 21 '18 at 10:08
Damien BannerotDamien Bannerot
2,35411121
2,35411121
add a comment |
add a comment |
For me the solution was different.
The app I was updating had previously used Fabric Crashlytics. When updating the app I converted the integration over to the Firebase Crashlytics integration (deleted the API keys from the build script, removed the Fabric with statement in the App Delegate, etc.)
I confirmed with Crashlytics support that if you are updating an app that was initially integrated with Crashlytics using the Fabric docs then you must continue to use that integration even if you have connected your app to Firebase and now use Firebase.
I pushed an update out where I reverted back to the integration outlined in the Fabric docs, and I now have Crashlytics data for this version in Firebase and Fabric.
answered Jan 1 at 18:08
KevinTydlackaKevinTydlacka
4211919
add a comment |
For me the solution was different.
The app I was updating had previously used Fabric Crashlytics. When updating the app I converted the integration over to the Firebase Crashlytics integration (deleted the API keys from the build script, removed the Fabric with statement in the App Delegate, etc.)
I confirmed with Crashlytics support that if you are updating an app that was initially integrated with Crashlytics using the Fabric docs then you must continue to use that integration even if you have connected your app to Firebase and now use Firebase.
I pushed an update out where I reverted back to the integration outlined in the Fabric docs, and I now have Crashlytics data for this version in Firebase and Fabric.
answered Jan 1 at 18:08
KevinTydlackaKevinTydlacka
4211919
add a comment |
For me the solution was different.
The app I was updating had previously used Fabric Crashlytics. When updating the app I converted the integration over to the Firebase Crashlytics integration (deleted the API keys from the build script, removed the Fabric with statement in the App Delegate, etc.)
I confirmed with Crashlytics support that if you are updating an app that was initially integrated with Crashlytics using the Fabric docs then you must continue to use that integration even if you have connected your app to Firebase and now use Firebase.
I pushed an update out where I reverted back to the integration outlined in the Fabric docs, and I now have Crashlytics data for this version in Firebase and Fabric.
answered Jan 1 at 18:08
KevinTydlackaKevinTydlacka
4211919
For me the solution was different.
The app I was updating had previously used Fabric Crashlytics. When updating the app I converted the integration over to the Firebase Crashlytics integration (deleted the API keys from the build script, removed the Fabric with statement in the App Delegate, etc.)
I confirmed with Crashlytics support that if you are updating an app that was initially integrated with Crashlytics using the Fabric docs then you must continue to use that integration even if you have connected your app to Firebase and now use Firebase.
I pushed an update out where I reverted back to the integration outlined in the Fabric docs, and I now have Crashlytics data for this version in Firebase and Fabric.
answered Jan 1 at 18:08
KevinTydlackaKevinTydlacka
4211919
answered Jan 1 at 18:08
KevinTydlackaKevinTydlacka
4211919
answered Jan 1 at 18:08
KevinTydlackaKevinTydlacka
4211919
answered Jan 1 at 18:08
KevinTydlackaKevinTydlacka
4211919
4211919
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53379543%2fmissing-version-in-fabric-crashlytics%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
I have the opposite - new version number immediately in the filter but no crash reports...
– Ewan
Nov 20 '18 at 20:57
@Ewan maybe you haven't had any crashes for that version? Try forcing one and see if it shows up (see Crashlytics Docs)
– KevinTydlacka
Jan 1 at 18:11
@Kevin - my big problem was releasing using './gradlew installRelease' rather than 'Build > Generate signed....' in AS. All working now stackoverflow.com/questions/53420776/…
– Ewan
Jan 2 at 18:25