@Amruthav,
This issue is reproduced and is logged in our database for further investigation. You will be notified here once any update is ready for sharing.
This issue is logged as:
NOTENET-3239 - HyperLink Address is empty despite there is a hyperlink address in the one note file
Hello Ahsan
Any updates on this ticket
Thanks
@Amruthav,
We already investigated your issue in details. Since the issue is a complex so it will take sometime to fix it precisely. We plan to fix it in Aspose.Note for .Net 21.7 release (the release will be published in July 2021).
The issues you have found earlier (filed as NOTENET-3239) have been fixed in this update(Downloads section / Nuget repos.). This message was posted using Bugs notification tool by alexei.s
The issue that we had reported here is still reproducible in Aspose. Note version 23.6. We’re not sure if it regressed in this version or if it was truly fixed. Could someone check and confirm?
@LinkTek1,
Could you please share the sample (runnable) code that you are using with Aspose.Note for .NET v23.6 to reproduce the issue? Also, please zip and attach the OneNote document. We will check your issue soon.
Hey @amjad.sahi, apologies for the delay in getting back to you. This totally missed our sights.
Here is the sample project: Aspose-10
The sample project contains the sample file 2020 weeks.one
.
@vikram.venugopal,
Thanks for providing us sample project and sample OneNote document.
Could you please try latest version, i.e., Aspose.Note for .NET 24.8. I have tested using your sample project with sample OneNote document and it works fine. I got the console output “All links are Okay”. If you find any issue with latest version of Aspose.Note for .NET API, let us know with details and sample. We will check your issue soon.
@amjad.sahi
We tried the sample project with Aspose.Notes 24.8 and it still gives us invalid links.
@vikram.venugopal,
Please provide sample app (complete source code without any compilation errors) along with resource files, so we can reproduce the issue on our end. Additionally, please specify which links are being retrieved as invalid links. You may also share screenshots to help us better understand the issue and resolve it promptly.
The sample project we provided before is working fine (without compilation errors and it detects the error), and can be used.
Aspose.Note finds those two text runs (“47560105” and “)”) which contain Hyperlinks value (and they shouldn’t)
image.png (175.3 KB)
@vikram.venugopal,
Thanks for the screenshot.
We will evaluate your issue thoroughly and get back to you soon.
@Amruthav,
Thanks for the screenshot and further details.
I tested your scenario/case using your sample project with your OneNote document “2020 weeks.one” using Aspose.Note 24.8 in licensing mode (using a valid license) and now I was able to reproduce your mentioned issue. I found some invalid links were retrieved (as per your screenshot) from the OneNote document. Please note, previously, I was not testing with a valid license.
We require thorough evaluation of the issue. We have opened the following new ticket(s) in our internal issue tracking system and will deliver their fixes according to the terms mentioned in Free Support Policies.
Issue ID(s): NOTENET-5849
You can obtain Paid Support Services if you need support on a priority basis, along with the direct access to our Paid Support management team.
Thanks @amjad.sahi, we will wait for your response on this.
@vikram.venugopal,
You are welcome. We will keep you posted with new updates/developments once available on it.
@amjad.sahi Any updates on NOTENET-5849?
@LinkTek1,
We are working over your issue and a rough ETA is Aspose.Note for .NET 24.11 which will be released before the end of this month. You will be notified once there is new updates or fixed version is published.
@LinkTek1, @vikram.venugopal,
The issue (Ticket ID: “NOTENET-5849”) has been resolved and fix will be included in the upcoming Aspose.Note for .NET 24.11 (November release).
Please stay tuned!
The issues you have found earlier (filed as NOTENET-5849) have been fixed in this update. This message was posted using Bugs notification tool by senua.remizova